Re: PPPoed crashed!!
From: Bikrant (bikrant_ml_at_wlink.com.np)
Date: 04/22/04
- Previous message: Thomas Elliott: "Re: Network Attack"
- Maybe in reply to: Bikrant Neupane: "PPPoed crashed!!"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
To: Matthew Seaman <m.seaman@infracaninophile.co.uk> Date: Thu, 22 Apr 2004 09:50:22 +0545
On Monday 19 April 2004 18:54, Matthew Seaman wrote:
> On Mon, Apr 19, 2004 at 04:13:51PM +0545, Bikrant wrote:
> > Here is the output of back trace
> > This GDB was configured as "i386-unknown-freebsd".
> > Core was generated by `pppoed'.
> > Program terminated with signal 11, Segmentation fault.
> > #0 0x280e461f in ?? ()
> > (gdb) bt
> > #0 0x280e461f in ?? ()
> > #1 0x280e48c1 in ?? ()
> > #2 0x280e46af in ?? ()
> > #3 0x280e48c1 in ?? ()
> > #4 0x280e4fd9 in ?? ()
> > #5 0x280e34dc in ?? ()
> > #6 0x280e3470 in ?? ()
> > #7 0x280dda10 in ?? ()
> > #8 0x280dd66d in ?? ()
> > #9 0x280c4cc9 in ?? ()
> > #10 0x280c4be5 in ?? ()
> > #11 0x8049640 in ?? ()
> > #12 0x804a22b in ?? ()
> > #13 0x8048dba in ?? ()
> > (gdb)
>
> Hmmm... Verb Sap. gdb backtraces tend to be a lot more useful if
> there's a copy of the executable with debugging symbols involved
> somewhere. If you've built world recently, there should be one in
> /usr/obj/usr/src/libexec/pppoed/pppoed -- and the gdb command line:
>
> # gdb /usr/obj/usr/src/libexec/pppoed/pppoed -c pppoed.core
>
> will load those symbols for you. (It doesn't matter if that core dump
> comes from a stripped version of the executable, only that they're
> both from the same build.)
>
Hi Matthew,
Sorry for late response. I'm running the same binary that came with the os. I
have not done any upgrades yet. I hope this one gives the clear picture.
Thanks for helping me use gdb :)
Here is the back trace result
pppoe# gdb -c pppoed.core-2004-04-13 /usr/libexec/pppoed
Core was generated by `pppoed'.
Program terminated with signal 11, Segmentation fault.
Reading symbols from /usr/lib/libnetgraph.so.1...(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 0x280e461f in isatty () from /usr/lib/libc.so.4
(gdb) bt
#0 0x280e461f in isatty () from /usr/lib/libc.so.4
#1 0x280e48c1 in isatty () from /usr/lib/libc.so.4
#2 0x280e46af in isatty () from /usr/lib/libc.so.4
#3 0x280e48c1 in isatty () from /usr/lib/libc.so.4
#4 0x280e4fd9 in malloc () from /usr/lib/libc.so.4
#5 0x280e34dc in __smakebuf () from /usr/lib/libc.so.4
#6 0x280e3470 in __swsetup () from /usr/lib/libc.so.4
#7 0x280dda10 in vfprintf () from /usr/lib/libc.so.4
#8 0x280dd66d in fprintf () from /usr/lib/libc.so.4
#9 0x280c4cc9 in vsyslog () from /usr/lib/libc.so.4
#10 0x280c4be5 in syslog () from /usr/lib/libc.so.4
#11 0x8049640 in NgRecvData ()
#12 0x804a22b in NgRecvData ()
#13 0x8048dba in NgRecvData ()
(gdb)
with regards,
Bikrant
> Cheers,
>
> Matthew
_______________________________________________
freebsd-isp@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-isp
To unsubscribe, send any mail to "freebsd-isp-unsubscribe@freebsd.org"
- Previous message: Thomas Elliott: "Re: Network Attack"
- Maybe in reply to: Bikrant Neupane: "PPPoed crashed!!"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|
