Unfortunately, this trace is nonsensical. It looks like this server
has been stripped? It must be getting arbitrary (nearest) symbols
or something. XAACopyArea cannot call XAAInitAccel, and the
sequence in fb is even worse. This does seem to indicate that
the problem occured in the fb (software rendering) module
though.
I wish there were a reproducable way to trigger this.
Mark.
On Tue, 30 Apr 2002 [EMAIL PROTECTED] wrote:
> Hello Mark,
>
> thanks for your hint. You can find below the backtrace on the corefile with
> modules loaded.
> Natascha
>
> (gdb) bt
> #0 0x40078a01 in __kill () from /lib/i686/libc.so.6 #1 0x400787da in raise
> (sig=6) at ../sysdeps/posix/raise.c:27 #2 0x40079f82 in abort () at
> ../sysdeps/generic/abort.c:88 #3 0x080d3220 in AbortServer () #4 0x080d46fc in
> FatalError ()
> #5 0x0808075e in xf86SigHandler () #6 <signal handler called> #7
> 0x0855718c in fbPolyline8 () #8 0x0a6d5ae8 in ?? ()
> #9 0x0856512b in fbCombineOutReverseC ()
> #10 0x08565714 in fbCombineAtopReverseC ()
> #11 0x08565a92 in fbCombineXorC ()
> #12 0x08565b6a in fbCopyArea ()
> #13 0x08587f48 in XAAInitAccel ()
> #14 0x08589ecc in XAACopyArea ()
> #15 0x08164a3b in miSpriteCopyArea ()
> #16 0x080b14bf in ProcCopyArea ()
> #17 0x080c4a4f in SProcCopyArea ()
> #18 0x080af497 in Dispatch ()
> #19 0x080bf311 in main ()
> #20 0x40066507 in __libc_start_main (main=0x80bedac <main>, argc ,
> ubp_av=0xbffffd34, init=0x806cc08 <_init>, fini=0x81747b0 <_fini>,
> rtld_fini=0x4000dc14 <_dl_fini>,
> stack_end=0xbffffd2c) at ../sysdeps/generic/libc-start.c:129 (gdb)
>
> >
> > With the special gdb you need to explicitly load the modules
> > in order to get a backtrace. Ie, before you get the backtrace enter
> >
> > module /usr/X11R6/lib/modules
> >
> > at the gdb prompt to indicate where to get the modules from.
> >
> >
> > Mark.
> >
> >
>
>
_______________________________________________
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert
