Ben Sferrazza <bsferraz_at_lsil.com> writes:
> Reading FvwmTaskBar
> core file header read successfully
> Reading ld.so.1
> Reading libm.so.1
> Reading libXpm.so.4.11
> Reading libpng.so.3
> Reading libSM.so.6
> Reading libICE.so.6
> Reading libXext.so.0
> Reading libX11.so.4
> Reading libsocket.so.1
> Reading libnsl.so.1
> Reading libc.so.1
> Reading libucb.so.1
> Reading libresolv.so.2
> Reading libelf.so.1
> Reading libdl.so.1
> Reading libmp.so.2
> Reading libc_psr.so.1
> Reading en_US.so.2
> Reading xlibi18n.so.2
> Reading xomEuro.so.2
> program terminated by signal ABRT (Abort)
> (/lsi/soft/forte/6.0-update1/WS6U1/bin/sparcv9/dbx) where
> =>[1] _kill(0x0, 0x6, 0xff033a30, 0x0, 0xffffffff, 0x0), at 0xff0182c4
> [2] abort(0xff033a30, 0x19, 0xff03b654, 0x0, 0xff210000, 0x0), at
> 0xfefb9468
> [3] PrintXErrorAndCoredump(0x66148, 0xffbeebb0, 0x62788, 0x0, 0x0,
> 0x0), at 0x34a88
> [4] ErrorHandler(0x66148, 0xffbeebb0, 0x20bfc, 0x0, 0xff033a30,
> 0xff1972e0), at 0x20c3c
> [5] _XError(0xff215a5c, 0x66ed0, 0xff210000, 0x66148, 0x40, 0x66148),
> at 0xff1a75c4
> [6] _XEventsQueued(0x66148, 0x66ed0, 0xff210000, 0x40, 0x0, 0x0), at
> 0xff19af00
> [7] XPending(0x66148, 0x66148, 0x1, 0x0, 0xff036abc, 0xffffffff), at
> 0xff19b69c
> [8] FPending(0x66148, 0x0, 0xff036abc, 0xff036abc, 0xff036abc, 0x6),
> at 0x34484
> [9] LoopOnEvents(0x4, 0x0, 0x1, 0x0, 0xffbeef08, 0x5d400), at 0x1f3a4
> [10] EndLessLoop(0x0, 0x436f0, 0x0, 0x42d, 0x17, 0xb4), at 0x1ca28
> [11] main(0x0, 0xffbef094, 0xffbef0b0, 0x610ec, 0x0, 0x0), at 0x1c908
OK, so now we know that the core is coming from FvwmTaskBar
when it enters the X Error handler. You posted the message
from the X error handler a while back it was:
> [FVWM][FvwmErrorHandler]: <<ERROR>> *** internal error ***
> [FVWM][FvwmErrorHandler]: <<ERROR>> Request 66, Error 8, EventType:4
>
> EventType can vary though it seems. I've seen 0, 28.
Request 66 = X_PolySegment
Error 8 = Badmatch
EventType 4 = buttonpress
EventType 28 = PropertyNotify
So, I think its drawing some lines and getting a badmatch error.
The eventtypes don't make sense to me.
I don't see any references to polysegment in FvwmTaskBar or
in the libs directory, so I'm a bit lost. Maybe one of our
X experts or FvwmTaskBar experts (Olivier?) can help me out?
> >I'm sorry, I should know exactly where the CDE stderr ends up,
> >but I hated CDE so much, I just had it removed from my workstation.
> >
> >I did run with it once...OK, I found it.
> >The fvwm output should be in $HOME/.xsession-errors
> >
> >Sorry to mislead you.
>
> PrintInfo Colors output doesn't seem to be going to ~/.xsession-errors.
> Maybe I should try running another fvwm process on top of the existing
> one from the command line, but redirect its output to another file. I
> suppose this is kind of what you were instructing me to do before with
> the '>'. Any ideas here?
No, you can only run one copy of fvwm at a time.
I'm not sure the output of PrintInfo Colors is important anymore,
the above information narrows the problem down a bit.
Lets see what one of our experts thinks is the next step.
--
Dan Espen E-mail: dane_at_mk.telcordia.com
--
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 Wed Dec 18 2002 - 19:46:41 GMT