RE: XWin 1.12.0-4 crash

["Michel Bardiaux" <MBardiaux@mediaxim.be>]

> From: Jon TURNEY

> Start the X server from a terminal using 'gdb --args XWin
-multiwindow', type 'r' to start the X
> server running, 

Did exactly that in a minty. Then in another one:

export DISPLAY=localhost:0.0
ssh -X -Y michel@besdev01 multi-gnome-terminal

> and 'bt full' after it crashes.

Which gives:

winProcEstablishConnection - winInitClipboard returned.
winClipboardProc - DISPLAY=:0.0
winInitMultiWindowWM - XOpenDisplay () returned and successfully opened
the display.
winClipboardProc - XOpenDisplay () returned and successfully opened the
display.
[New Thread 1452.0x350]
winMultiWindowXMsgProc - XOpenDisplay () returned and successfully
opened the display.
[New Thread 1452.0xcf0]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1452.0xf04]
0x0040a41e in winXIconToHICON ()
(gdb) bt full
#0  0x0040a41e in winXIconToHICON ()
No symbol table info available.
#1  0x0040a6ab in winUpdateIcon ()
No symbol table info available.
#2  0x0041f5e7 in UpdateIcon.clone.3 ()
No symbol table info available.
#3  0x004210d0 in winMultiWindowWMProc ()
No symbol table info available.
#4  0x610fbd52 in pthread::thread_init_wrapper(void*) () from
/cygdrive/c/cygwin/bin/cygwin1.dll
No symbol table info available.
#5  0x610868f2 in thread_wrapper(void*) () from
/cygdrive/c/cygwin/bin/cygwin1.dll
No symbol table info available.
Backtrace stopped: Not enough registers or memory available to unwind
further

Note that if I invoke xclock instead of multi-gnome-terminal, it works.
Ditto xterm, emacs, and fortunately all my personal apps!

Greetings,
(s) M. Bardiaux

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://x.cygwin.com/docs/
FAQ:                   http://x.cygwin.com/docs/faq/