Dan D Niles <dan_at_more.net> writes:
>
> Apparenly the default somewhere in slackware 8 is to not do
> cores. I added 'ulimit -c unlimited' to my .xsession and got
> a core.
>
> gdb `which fvwm2` core
> where
>
> produced:
>
> #0 0x807e54a in XMapRaised ()
> #1 0xbffff118 in ?? ()
> #2 0x807fa5d in XMapRaised ()
> #3 0x806717e in XMapRaised ()
> #4 0x80670f1 in XMapRaised ()
> #5 0x8069282 in XMapRaised ()
> #6 0x8069318 in XMapRaised ()
> #7 0x808603f in XMapRaised ()
> #8 0x401742eb in __libc_start_main (main=0x8084d20 <XMapRaised+231828>,
> argc=1, ubp_av=0xbffff794, init=0x804b374 <_init>, fini=0x809197c <_fini>
> ,
> rtld_fini=0x4000c130 <_dl_fini>, stack_end=0xbffff78c)
> at ../sysdeps/generic/libc-start.c:129
I don't think anyone is going to be able to get anywhere with that.
Note that the stack doesn't lead back up to main() and
that there are bunch of functions at different addresses all claiming
to be XMapRaised.
I see this frequently, but I haven't got a good list of the causes.
Perhaps fvwm just needs to be recompiled with -g, or your gdb
needed to be upgraded to match the gcc that this was compiled with,
or the fvwm2 in your path doesn't match the core file, or the file
system the core file is on ran out of space and got truncated.
--
Dan Espen
444 Hoes Lane Room RRC 1C-214 E-mail: dane_at_mk.telcordia.com
Piscataway, NJ 08854 Phone: (732) 699-5570
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Thu Oct 25 2001 - 18:58:19 BST