On Fri, 28 Mar 2003, Adri Frick wrote:
>
> On Fri, 28 Mar 2003, Mark Vojkovich wrote:
>
> > I don't suppose you know how to use gdb so you can find
> > where it crashed at?
>
> Nope, don't know gdb, but that has never stopped me before. (That's what
> man and google are for):
>
> # gdb XFree86 ./XFree86.core
> GNU gdb 4.18 (FreeBSD)
> <blahblahblah GPL notice stuff>
> This GDB was configured as "i386-unknown-freebsd"...
> (no debugging symbols found)...
> Core was generated by `XFree86'.
> Program terminated with signal 6, Abort trap.
> Reading symbols from /usr/lib/libz.so.2...(no debugging symbols
> found)...done.
> Reading symbols from /usr/lib/libm.so.2...(no debugging symbols
> found)...done.
> Reading symbols from /usr/lib/libc.so.4...(no debugging symbols
> found)...done.
> Reading symbols from /usr/libexec/ld-elf.so.1...(no debugging symbols
> found)...
> done.
> #0 0x28214b78 in kill () from /usr/lib/libc.so.4
> (gdb)
>
> (I assumed by the gdb prompt it was done. Hope that was right, as it
> seemed a little short.)
>
Enter "bt" from the gdb prompt to get a stacktrace. This
will show the progression of functions leading up to this.
Ones that are in modules won't show up unless you have a special
XFree86 module-aware version of gdb, but if I'm correct about
the crash being in the core server, then you should be able
to see all of the relevant stuff with the regular gdb.
Mark.
_______________________________________________
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86
