Re: Some problems with GNUstep and Paje

[Tony Reix]

Thanks Nicolas,


{ hm, what's Paje ?

Benhur answered this question.
Maybe I could add that Paje is dedicated to tracing programs parallelized
by means of Threads or MPI and that we plan to use it for tracing the NPTL
library (which provides the POSIX Threads to Linux now).

Look at : http://nptl.bullopensource.org/  for details.


{ > and I get the following message:
{ >   Xlib:  extension "MIT-SHM" missing on display "txgia2:0.0".
{ >   2004-08-20 08:59:55.245 Paje[3299] WARNING - XGServer is unable to 

{ Well, if that works with the PC/Linux, that's probably just a X11 problem.
{ You could try to set the default to explicitely remove the shm use:
{ 
{ defaults write NSGlobalDomain XWindowBufferUseXShm NO

That made the "MIT-SHM ...." message disappear. But Paje still dont' appear on 
my Xterminal.
I've waited a while (10-15 mn) and I noticed that the "font_cacher"
process is still running and consumming CPU (~ 3 mn during these 15 mn)
and my Xterminal is still slower than usually.

When I killed this font_cacher process, I got:

[root@nptl Paje]# 2004-08-23 09:47:44.724 Paje[15541] File NSData.m: 153. In 
readContentsOfFile Open (/root/GNUstep/Library/Fonts/Cache/txgia2:0.0) attempt 
failed - No such file or directory
2004-08-23 09:47:44.724 Paje[15541] Error - font cache doesn't exist
2004-08-23 09:47:44.740 Paje[15541]
I couldn't contact the notification server for txgia2.frec.bull.fr -
so I'm attempting to to start one - which will take a few seconds.
Trying to launch gdnc from /usr/local/GNUstep/System/Tools or a 
machine/operating-system subdirectory.
It is recommended that you start the notification server (gdnc) either at login 
or (better) when your computer is started up.
2004-08-23 09:47:49.786 Paje[15541] XGFont: selected font: Helvetica at 
12.000000 ((nil)) is not available.
2004-08-23 09:47:49.786 Paje[15541] The font specified for NSFont, Helvetica, 
can't be found.
2004-08-23 09:47:49.786 Paje[15541] XGFont: selected font: Helvetica at 
12.000000 ((nil)) is not available.
....
Then, due to another bug that appears when too much characters are written to
the Xterm and too fast, the Xterm hung.

Any more idea ?  (maybe I should use a PC ....)


Amicalement/Regards,

Tony