Thanks for the stacktrace. Unfortunately, these appear
to be in modules. The XFree86 module-enabled version of gdb
would be able to resolve the module symbols "??". I don't
know if you want to go through the work to get that going
or not (assuming it even runs on FreeBSD. I don't know what's
involved in getting it to run on FreeBSD).
All I can say at the moment is that I can't reproduce
this under Linux and the Linux and FreeBSD "nv" modules
should be identical.
Mark.
On Fri, 28 Mar 2003, Adri Frick wrote:
>
> That looks much more like a stacktrace (thanks!):
>
> #0 0x28214b78 in kill () from /usr/lib/libc.so.4
> #1 0x28255742 in abort () from /usr/lib/libc.so.4
> #2 0x806c6e5 in ddxGiveUp ()
> #3 0x806c78a in AbortDDX ()
> #4 0x80d3de0 in AbortServer ()
> #5 0x80d51ad in FatalError ()
> #6 0x807f71a in xf86SigHandler ()
> #7 0xbfbfffac in ?? ()
> #8 0x870468c in ?? ()
> #9 0x8703b1e in ?? ()
> #10 0x87028af in ?? ()
> #11 0x8705408 in ?? ()
> #12 0x87054e6 in ?? ()
> #13 0x8703505 in ?? ()
> #14 0x806baa8 in InitOutput ()
> #15 0x80bf352 in main ()
> #16 0x806b1c1 in _start ()
>
>
>
> On Fri, 28 Mar 2003, Mark Vojkovich wrote:
>
> > Enter "bt" from the gdb prompt to get a stacktrace. This
> > will show the progression of functions leading up to this.
>
>
_______________________________________________
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86
