Hello,
I updated my Cygwin with the latest available from the setup.exe.
Now XWin.exe gets a Signal 11 (Segmentation violation) when a font switch (-fn)
is on the command line.
Command:
$ ssh -Y myaix aixterm -fullcursor -geometry 81x30-125+93 -e
/usr/local/bin/max.pl
Is OK.
$ ssh -Y myaix
The previous version, that was stable for xorg-server was 1.8.2-1,
according to setup.log.
The gdb stack trace is not very talkative:
...
Loaded symbols for /usr/bin/cygXrender-1.dll
[Switching to thread 8788.0x2740]
(gdb) c
Continuing.
(no debugging symbols found)
Program received signal
I did a bit of further reseach.
It looks like it does not have anything to do with the way the font server is
queried,
but rather the way the startup is done.
When I have the font server added during the XWin startup - either in the
startxwin.bat, or a bash-script I call from there, the XWin
I managed to work around it.
In the startup of XWin I start a few windows.
In one of them I add the font server after a bit of sleep to settle down
XWin.
Now the XWin does not SIGSEGV any more why so ever.
Here are the scripts I use to start up my X environment
Burkhard
Startxwin.bat:
@echo
Rejoiced too early.
When I start an application that uses a font that is not on the font
server XWin crashes again with the same stack trace I already sent you.
Burkhard
_
Geschaeftsfuehrer/Managing
