Re: X segmentation fault when particular application attempts to open a window
Jon, thank you for the update! XWin is working as before. I appreciate your prompt action very much. Yusuke >On 25/04/2012 22:45, Keith Lindsay wrote: >> On 4/25/2012 2:20 PM, Keith Lindsay wrote: >>> I'm running a data analysis program called ferret on a remote machine >>> that I've logged on to with "ssh -X". When the program attempts to >>> create a window, the Cygwin/X server crashes with a segmentation fault. >>> The seg fault is reproducible. >>> >>> xclock works fine from the same remote machine. >>> >>> This is with version 1.12.0-4 of xorg-server. >>> >>> ferret has worked with some previous versions of the Cygwin/X server, >>> but I'm not certain about the precise version where the breakage >>> occurred. I backed up one version and encountered the same problem. >>> >>> I've attached the output of "cygcheck -c", the file >>> /var/log/xwin/XWin.0.log, and the output of a gdb that is attached to >>> the XWin process when it crashes. >> >> I realized that I can back up to other versions of xorg-server by >> installing >> from the local directory that contains previous version downloads. I have >> discovered that ferret works fine with version 1.12.0-1 of xorg-server >> (built >> 2012-03-12) and generates the segmentation violation with version 1.12.0-2 >> (built 2012-04-04). > >Thanks for the excellent bug report. > >I've uploaded 1.12.0-5 which hopefully contains a fix for this crash. > >This crash was caused by the server being unable to find the bitmap which the >application wants to use for it's icon, it's not clear why this is happening, >so I would be interested to know if the application icon is correct or not. > >-- >Jon TURNEY >Volunteer Cygwin/X X Server maintainer -- 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/
Re: X segmentation fault when particular application attempts to open a window
On 04/26/2012 12:15 PM, Jon TURNEY wrote: Thanks for the excellent bug report. You're welcome. Thank you for the prompt response. I've uploaded 1.12.0-5 which hopefully contains a fix for this crash. Good news, ferret works fine with 1.12.0-5. This crash was caused by the server being unable to find the bitmap which the application wants to use for it's icon, it's not clear why this is happening, so I would be interested to know if the application icon is correct or not. The icon that appears on the taskbar when I open a ferret window is a generic Xorg icon. I'm not certain if there is an actual icon for ferret that should be appearing. I get a similar generic icon when the X server displaying the window is being run on Linux, so this behavoir is not unique to Cygwin. So it seems like a feature of the application, or the installation of the application. The application works otherwise. Thanks again for the prompt response and fix, Keith -- 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/
Re: xlogo crashes XWin with Fatal Error (Segmentation Fault)
Re: xlogo crashes XWin with Fatal Error (Segmentation Fault) 2012.04.26.18:13:33 UT Hey cygwin-x folks, I have not had notable difficulties with XWin-1.12.0-4. Just about everything that I have done with it over the past few days has been fine. However, when I read Yusuke's post, I thought that I should try one of those old-timey X-programs to see whether it would crash. I've been able to reproduce an XWin crash similar to the one experienced by Yusuke. My XWin did _not_ fail when I was running octave with either the fltk or its usual gnuplot backends. I was also able to run xfig with no problem. This was a crash caused when I opened the xcalc program. I'm not certain that I understand his experiment with two terminal windows as a method of narrowing the difficulty to the -multiwindow option. However like Yusuke, I am starting XWin with the -mulitwindow option. The crash I observed was with just a single xterm, and then the xcalc program. Other programs that opened x-windows seemed fine. In this instance, I had the debugging symbols available, and collected information from a backtrace using (gdb). I've attached gdb.xwin.20120426.txt and my XWin.0.20120426.log. I did not see anything interesting in the xwin0-log, and my (gdb) backtrace is just the output from my glance at Jon Turney's recipe. I'm tossing it in this list in case it helps better-informed folks to track down the difficulty with XWin-1.12.0-4. If there is more specific or nuanced stuff that I can log with (gdb) to provide more information, please e-mail me. George gbarrick_at_walsh_dot_edu Continuing. Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 2528.0xf34] 0x0040a41e in winXIconToHICON (pDisplay=0x20279a30, id=10485779, iconSize=) at /opt/wip/cygport-git/xorg-server/xorg-server-1.12.0-4/src/xserver-cygwin-1.12.0-4/hw/xwin/winmultiwindowicons.c:535 535 /opt/wip/cygport-git/xorg-server/xorg-server-1.12.0-4/src/xserver-cygwin-1.12.0-4/hw/xwin/winmultiwindowicons.c: No such file or directory. in /opt/wip/cygport-git/xorg-server/xorg-server-1.12.0-4/src/xserver-cygwin-1.12.0-4/hw/xwin/winmultiwindowicons.c #0 0x0040a41e in winXIconToHICON (pDisplay=0x20279a30, id=10485779, iconSize=) at /opt/wip/cygport-git/xorg-server/xorg-server-1.12.0-4/src/xserver-cygwin-1.12.0-4/hw/xwin/winmultiwindowicons.c:535 root = y = depth = xImageIcon = 0x0 x = width = height = border_width = xImageMask = 0x0 mask = image = imageMask = dst = src = planes = 1 bpp = 32 i = biggest_size = hDC = ii = hints = 0x203ae1e8 hIcon = 0x0 biggest_icon = _XA_NET_WM_ICON = generation = icon = icon_data = 0x0 size = 0 type = 0 format = 0 left = #1 0x0040a6ab in winUpdateIcon ( hWnd=, hWnd@entry=, pDisplay=, id=, hIconNew=) at /opt/wip/cygport-git/xorg-server/xorg-server-1.12.0-4/src/xserver-cygwin-1.12.0-4/hw/xwin/winmultiwindowicons.c:560 hIcon = hIconSmall = 0x0 hIconOld = A debugging session is active. Inferior 1 [process 2528] will be detached. Quit anyway? (y or n) error return /netrel/src/gdb-7.3.50-3/gdb/windows-nat.c:1251 was 31 Quitting: Can't detach process 2528 (error 5) XWin.0.20120426.log Description: XWin.0.20120426.log -- 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/
[ANNOUNCEMENT] Updated: xorg-server-1.12.0-5
The following packages have been updated in the Cygwin distribution: *** xorg-server-1.12.0-5 *** xorg-server-common-1.12.0-5 *** xorg-server-dmx-1.12.0-5 *** xorg-server-extra-1.12.0-5 *** xorg-server-devel-1.12.0-5 These packages contain XWin and the other X.Org X11 servers. The following cygwin-specific changes have been made since 1.12.0-4: * Fix a crash which could occur in WM_HINTS bitmap icon conversion (Reported by Keith Lindsay, Yusuke Tamura and others) * stdout and stderr for processes started from the notification area icon are now written to the X server log * Remove the llvmpipe/softpipe testing facility using the GALLIUM_DRIVER environment variable 696546cad78a343467ddf4dafbdb8ebb *xorg-server-1.12.0-5.tar.bz2 a4e2688aac776d4857b585af1c30e3bd *xorg-server-common-1.12.0-5.tar.bz2 96e6cd66404a1a3f0f12fe7a5663ae48 *xorg-server-devel-1.12.0-5.tar.bz2 aa008cd283e392eb50f5a33d706fb249 *xorg-server-dmx-1.12.0-5.tar.bz2 b54a699855c844dd536e848195c50a61 *xorg-server-extra-1.12.0-5.tar.bz2 2ffceecd814981724ce6ec6470ea9da9 *xorg-server-1.12.0-5-src.tar.bz2 -- 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/
Re: Fatal Error (Segmentation Fault) only while viewing the LVM GUI
On 26/04/2012 14:23, Jon TURNEY wrote: > On 26/04/2012 14:18, Jon TURNEY wrote: >> On 25/04/2012 19:25, Carlo.DiCocco wrote: >>> I think I may have found a bug. I am connecting to a remote Linux server >>> from my Windows desktop and attempting to use some of the GUI tools on the >>> remote server. The "xclock" GUI displays fine. The Oracle "dbca" GUI >>> displays fine. The LVM "system-config-lvm" GUI displays and works fine, >>> but cygwin generates a fatal error window due to a segmentation fault. >> >>> The following command displays the GUI, but reports a fatal error: >>> >>> [root@aorahdev ~]# system-config-lvm >> >>> [ 64144.546] Segmentation fault at address 0x44 >>> [ 64144.546] Fatal server error: >>> [ 64144.546] Caught signal 11 (Segmentation fault). Server aborting >>> [ 64144.546] Server terminated with error (1). Closing log file. >> >> Thanks for reporting this problem. >> >> I was not able to reproduce this crash using system-config-lvm 1.1.16, on >> Fedora 15. Perhaps you can provide details on the remote server and >> system-config-lvm version you are using? >> >> It would be very helpful if you could follow the instructions at [1] to use >> gdb to get a backtrace for the X server when it crashes. > > Oops > > [1] http://x.cygwin.com/devel/backtrace.html It seems quite likely this is the same crash as reported at [1], so it's probably worth testing X server 1.12.0-5 to see if it's fixed there, first. [1] http://cygwin.com/ml/cygwin-xfree/2012-04/msg00097.html -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- 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/
Re: XWin 1.12.0-4 crash
On 23/04/2012 12:55, Michel Bardiaux wrote: > Nothing much to add to the 2 attached files - except that my X worked > fine until the last update. Will try reverting to previous version. Mentioning the name of the application which caused the crash (multi-gnome-terminal) would have helped. On 23/04/2012 14:03, Michel Bardiaux wrote: > Yes, it is a crash at startup. So, in fact, it's not a crash when the X server is started, but when you try to run the application multi-gnome-terminal? On 26/04/2012 15:54, Michel Bardiaux wrote: >> 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 It looks like this is the same crash as reported at [1], and should be fixed in X server 1.12.0-5. [1] http://cygwin.com/ml/cygwin-xfree/2012-04/msg00097.html -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- 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/
Re: X segmentation fault when particular application attempts to open a window
On 25/04/2012 22:45, Keith Lindsay wrote: > On 4/25/2012 2:20 PM, Keith Lindsay wrote: >> I'm running a data analysis program called ferret on a remote machine >> that I've logged on to with "ssh -X". When the program attempts to >> create a window, the Cygwin/X server crashes with a segmentation fault. >> The seg fault is reproducible. >> >> xclock works fine from the same remote machine. >> >> This is with version 1.12.0-4 of xorg-server. >> >> ferret has worked with some previous versions of the Cygwin/X server, >> but I'm not certain about the precise version where the breakage >> occurred. I backed up one version and encountered the same problem. >> >> I've attached the output of "cygcheck -c", the file >> /var/log/xwin/XWin.0.log, and the output of a gdb that is attached to >> the XWin process when it crashes. > > I realized that I can back up to other versions of xorg-server by installing > from the local directory that contains previous version downloads. I have > discovered that ferret works fine with version 1.12.0-1 of xorg-server (built > 2012-03-12) and generates the segmentation violation with version 1.12.0-2 > (built 2012-04-04). Thanks for the excellent bug report. I've uploaded 1.12.0-5 which hopefully contains a fix for this crash. This crash was caused by the server being unable to find the bitmap which the application wants to use for it's icon, it's not clear why this is happening, so I would be interested to know if the application icon is correct or not. -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- 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/
xlogo crahes XWin with Fatal Error (Segmentation Fault)
Dear sirs, Some days ago I updated the cygwin system by 'setup.exe', expecting some "GL" problems are fixed. Since then XWin crashes with some application programs. One of the most simplest is 'xlogo'. What I have done is as follows; Start [XWin Server] (wait some time for bringing up xterm), then enter 'xlogo' in xterm, [Cygwin/X] window appears immediately. It says, > A fatal error ... > > Caught signal 11 (Segmentation fault). ... > > Please open /var/log/xwin/XWin.0.log ... > > Vendor: .. > Release: 1.12.0.0 > Contact: .. > Package: version 1.12.0-4 built 2012-04-17 > > XWin was started ... > > X :0 -multiwindow /var/log/xwin/XWin.0.log does not report anything important at all. OK, I tried 'X :0 -multiwindow' on one terminal, and on the other terminal $ export DISPLAY=:0.0 $ xlogo then, the message appears on one therminal; >Segmentation fault at address 0x44 > >Fatal server error: >Caught signal 11 (Segmentation fault). Server aborting > >Server terminated with error (1). Closing log file. >winDeinitMultiWindowWM - Noting shutdown in progress >winMsgWindowProc - pthread_mutex_unlock () failed: 1 while entering 'X :0' on one terminal, entring 'xlogo' on the other, there was no fatal problem. Obviously '-multiwindow' does something wrong. Keith Lindsay's post might be helpfull as workaround, but I cannot rollback to the 'version 1.12.0-1 of xorg-server (built 2012-03-12)' using 'setup.exe', April 25, 2012 21:45 Re: X segmentation fault when particular application attempts to open a window http://cygwin.com/ml/cygwin-xfree/2012-04/msg00100.html best regards, Yusuke Tamura --- -- 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/
RE: XWin 1.12.0-4 crash
> 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/
Re: Fatal Error (Segmentation Fault) only while viewing the LVM GUI
On 26/04/2012 14:18, Jon TURNEY wrote: > On 25/04/2012 19:25, Carlo.DiCocco wrote: >> I think I may have found a bug. I am connecting to a remote Linux server >> from my Windows desktop and attempting to use some of the GUI tools on the >> remote server. The "xclock" GUI displays fine. The Oracle "dbca" GUI >> displays fine. The LVM "system-config-lvm" GUI displays and works fine, >> but cygwin generates a fatal error window due to a segmentation fault. > >> The following command displays the GUI, but reports a fatal error: >> >> [root@aorahdev ~]# system-config-lvm > >> [ 64144.546] Segmentation fault at address 0x44 >> [ 64144.546] Fatal server error: >> [ 64144.546] Caught signal 11 (Segmentation fault). Server aborting >> [ 64144.546] Server terminated with error (1). Closing log file. > > Thanks for reporting this problem. > > I was not able to reproduce this crash using system-config-lvm 1.1.16, on > Fedora 15. Perhaps you can provide details on the remote server and > system-config-lvm version you are using? > > It would be very helpful if you could follow the instructions at [1] to use > gdb to get a backtrace for the X server when it crashes. Oops [1] http://x.cygwin.com/devel/backtrace.html -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- 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/
Re: XWin 1.12.0-4 crash
On 23/04/2012 14:03, Michel Bardiaux wrote: > Yes, it is a crash at startup. > > I could not find XWin.exe.stackdump anywhere on my hard drive. I have > attached the bat script (renamed into .txt) used to start cygwin/X, > maybe I need to modify it. > > Would it work to add > > CYGWIN='error_start=c:\cygwin\bin\dumper.exe' > > in the system environment (meaning, via the control panel), to have a > core file that I could then open with gdb? No, I don't think that would work (for various uninteresting reasons) Start the X server from a terminal using 'gdb --args XWin -multiwindow', type 'r' to start the X server running, and 'bt full' after it crashes. -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- 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/
Re: Fatal Error (Segmentation Fault) only while viewing the LVM GUI
On 25/04/2012 19:25, Carlo.DiCocco wrote: > I think I may have found a bug. I am connecting to a remote Linux server > from my Windows desktop and attempting to use some of the GUI tools on the > remote server. The "xclock" GUI displays fine. The Oracle "dbca" GUI > displays fine. The LVM "system-config-lvm" GUI displays and works fine, > but cygwin generates a fatal error window due to a segmentation fault. > The following command displays the GUI, but reports a fatal error: > > [root@aorahdev ~]# system-config-lvm > [ 64144.546] Segmentation fault at address 0x44 > [ 64144.546] Fatal server error: > [ 64144.546] Caught signal 11 (Segmentation fault). Server aborting > [ 64144.546] Server terminated with error (1). Closing log file. Thanks for reporting this problem. I was not able to reproduce this crash using system-config-lvm 1.1.16, on Fedora 15. Perhaps you can provide details on the remote server and system-config-lvm version you are using? It would be very helpful if you could follow the instructions at [1] to use gdb to get a backtrace for the X server when it crashes. -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- 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/
