Re: Need help debugging Windowmaker coredump
Hi Jonathon, On Wed, Oct 30, 2002 at 01:58:23AM +, Jonathon McKitrick wrote: Here's what I have so far: - Program terminated with signal 11, Segmentation fault.^M [snip] #0 0x80b4545 in WMGetFromPLDictionary (plist=0x0, key=0x8137b50)^M ---Type return to continue, or q return to quit---^M at proplist.c:1429^M 1429wassertrv(plist-type==WPLDictionary, NULL);^M (gdb) bt^M #0 0x80b4545 in WMGetFromPLDictionary (plist=0x0, key=0x8137b50)^M at proplist.c:1429^M #1 0x807ebf9 in wMenuRestoreState (scr=0x80f8400) at menu.c:2720^M #2 0x8093844 in StartUp (defaultScreenOnly=0) at startup.c:977^M #3 0x807898b in main (argc=1, argv=0xbfbffbe4) at main.c:797^M (gdb) quit^M --- I looked at the source, but it seems like the assert would have caught the null plist pointer. No, because it asserts that plist-type should be equal to WPLDictionary, without checking for a NULL plist argument. This code is from the WINGs source that comes with windowmaker. OK, first of all I don't run WindowMaker so this is not going to be up my alley, but I can guess, and maybe get you going a little further: It seems that plist == NULL. If you type 'frame 1' in gdb after the bt you should get the line where WMGetFromPLDictionary is called, this is at menu.c:2720 as gdb says. The NULL pointer seems to be scr-session_state, in other words, there doesn't seem to be a session state loaded. My rough guess is that something in your .wmaker startup dir is screwed. Have you tried to remove that to test if it works then? Otherwise you need to trace the code and try to figure out why scr-session_state isn't being initialized like it should. Any idea what could be causing this? Other than the above hints, no, sorry. You'll probably get better help from the wmaker mailing list. --Stijn -- Computer games don't affect kids; I mean if Pac-Man affected us as kids, we'd all be running around in darkened rooms, munching magic pills and listening to repetitive electronic music. -- Kristian Wilson, Nintendo, Inc., 1989 msg07092/pgp0.pgp Description: PGP signature
Need help debugging Windowmaker coredump
Hi all, I'm trying to figure out how to get more debugging info out of my core dump. Here's all I have so far: local:~ gdb -c wmaker.core GNU gdb 4.18 (FreeBSD) Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-unknown-freebsd. Core was generated by `wmaker'. Program terminated with signal 11, Segmentation fault. #0 0x80967d6 in ?? () (gdb) where #0 0x80967d6 in ?? () #1 0x80706cb in ?? () #2 0x807f975 in ?? () #3 0x806c3d8 in ?? () #4 0x804d219 in ?? () (gdb) This obviously isn't much help. What do I need to include in the port build to get more debugging info so I can post a helpful core dump? NOTE: Please CC me, as I am not currently subscribed. Thanks. jm -- My other computer is your windows box. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Need help debugging Windowmaker coredump
On Tue, Oct 29, 2002 at 12:06:44PM +, Jonathon McKitrick wrote: Hi all, I'm trying to figure out how to get more debugging info out of my core dump. Here's all I have so far: local:~ gdb -c wmaker.core GNU gdb 4.18 (FreeBSD) Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-unknown-freebsd. Core was generated by `wmaker'. Program terminated with signal 11, Segmentation fault. #0 0x80967d6 in ?? () (gdb) where #0 0x80967d6 in ?? () #1 0x80706cb in ?? () #2 0x807f975 in ?? () #3 0x806c3d8 in ?? () #4 0x804d219 in ?? () (gdb) This obviously isn't much help. What do I need to include in the port build to get more debugging info so I can post a helpful core dump? NOTE: Please CC me, as I am not currently subscribed. Thanks. You want to pass the -g option to the compiler, to get gdb to emit source file names and linenumbers. Most of the time something like this works: /usr/ports/x11-wm/windowmaker# make CFLAGS=-g STRIP= all install But this depends on whether the port honors your custom CFLAGS. Note that usually you don't have to install the debug version, you can also run the resulting binary from the work/windowmaker-0.xxx/... subdirs. Hope this helps, --Stijn -- Fairy tales do not tell children that dragons exist. Children already know dragons exist. Fairy tales tell children the dragons can be killed. -- G.K. Chesterton msg06945/pgp0.pgp Description: PGP signature
Re: Need help debugging Windowmaker coredump
Here's what I have so far: - Program terminated with signal 11, Segmentation fault.^M Reading symbols from /usr/X11R6/lib/libwraster.so.4...done.^M Reading symbols from /usr/local/lib/libtiff.so.4...done.^M Reading symbols from /usr/X11R6/lib/libXpm.so.4...done.^M Reading symbols from /usr/local/lib/libHermes.so.1...done.^M Reading symbols from /usr/local/lib/libpng.so.5...done.^M Reading symbols from /usr/lib/libz.so.2...done.^M Reading symbols from /usr/local/lib/libjpeg.so.9...done.^M Reading symbols from /usr/local/lib/libungif.so.5...done.^M Reading symbols from /usr/X11R6/lib/libXext.so.6...done.^M Reading symbols from /usr/X11R6/lib/libX11.so.6...done.^M Reading symbols from /usr/lib/libm.so.2...done.^M Reading symbols from /usr/local/lib/libintl.so.4...done.^M Reading symbols from /usr/lib/libxpg4.so.3...done.^M Reading symbols from /usr/lib/libc.so.4...done.^M Reading symbols from /usr/X11R6/lib/libXThrStub.so.6...done.^M Reading symbols from /usr/local/lib/libiconv.so.3...done.^M Reading symbols from /usr/X11R6/lib/X11/locale/common/xlcDef.so.2...done.^M Reading symbols from /usr/X11R6/lib/X11/locale/common/ximcp.so.2...done.^M Reading symbols from /usr/libexec/ld-elf.so.1...done.^M #0 0x80b4545 in WMGetFromPLDictionary (plist=0x0, key=0x8137b50)^M ---Type return to continue, or q return to quit---^M at proplist.c:1429^M 1429wassertrv(plist-type==WPLDictionary, NULL);^M (gdb) bt^M #0 0x80b4545 in WMGetFromPLDictionary (plist=0x0, key=0x8137b50)^M at proplist.c:1429^M #1 0x807ebf9 in wMenuRestoreState (scr=0x80f8400) at menu.c:2720^M #2 0x8093844 in StartUp (defaultScreenOnly=0) at startup.c:977^M #3 0x807898b in main (argc=1, argv=0xbfbffbe4) at main.c:797^M (gdb) quit^M --- I looked at the source, but it seems like the assert would have caught the null plist pointer. This code is from the WINGs source that comes with windowmaker. Any idea what could be causing this? jm -- My other computer is your Windows box. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
