Dan Espen writes:
>
> 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.
>
> [clip]
I didn't think that looked very useful. The fvwm2 binary was
being stripped so even though it was compiled with -g there
was no symbol info. Here is a fixed gdb output:
#0 0x809354a in setup_window_placement (tmp_win=0x80f02b0, pstyle=0xbffff1c0)
at add_window.c:578
#1 0x809533a in AddWindow (w=23069835, ReuseWin=0x0) at add_window.c:1426
#2 0x8073402 in HandleMapRequestKeepRaised (KeepRaised=0, ReuseWin=0x0)
at events.c:1040
#3 0x8073340 in HandleMapRequest () at events.c:1004
#4 0x80764e2 in DispatchEvent (preserve_Tmp_win=0) at events.c:2785
#5 0x80765aa in HandleEvents () at events.c:2838
#6 0x809dd7f in main (argc=2, argv=0xbffff794) at fvwm.c:718
#7 0x401742eb in __libc_start_main (main=0x809c4d0 <main>, argc=1,
ubp_av=0xbffff794, init=0x804b3dc <_init>, fini=0x80adc3c <_fini>,
rtld_fini=0x4000c130 <_dl_fini>, stack_end=0xbffff78c)
at ../sysdeps/generic/libc-start.c:129
--
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 Fri Oct 26 2001 - 14:35:06 BST