Date: Mon, 19 Feb 2001 07:44:28 +1100 From: Peter Jeremy <peter.jeremy@alcatel.com.au> To: freebsd-alpha@freebsd.org Subject: ppp core-dumping in kernel space? Message-ID: <20010219074428.E70642@gsmx07.alcatel.com.au>
next in thread | raw e-mail | index | archive | help
I'm running -current from 8th February on a Multia and ppp is regularly core-dumping (sigmentation violation). The core dump contents seem consistent from the couple of different core's that I've studied. gdb against ppp gives the following: multia# gdb /usr/obj/usr/src/usr.sbin/ppp/ppp /ppp.core GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "alpha-unknown-freebsd"... Core was generated by `ppp'. Program terminated with signal 11, Segmentation fault. warning: Hit heuristic-fence-post without finding warning: enclosing function for address 0xfffffc00003af9c0 This warning occurs if you are debugging a function without any symbols (for example, in a stripped executable). In that case, you may wish to increase the size of the search with the `set heuristic-fence-post' command. Otherwise, you told GDB there was a function where there isn't one, or (more likely) you have encountered a bug in GDB. #0 0xfffffc00003af9c0 in ?? () (gdb) where #0 0xfffffc00003af9c0 in ?? () warning: Hit heuristic-fence-post without finding warning: enclosing function for address 0x11ffbfc4 (gdb) info regi v0 0xa 10 t0 0xfffffe00033ba940 -2198969013952 t1 0x0 0 t2 0xfffffc00005e8be0 -4398040314912 t3 0x1 1 t4 0x2000 8192 t5 0x0 0 t6 0xfffffe00033babe8 -2198969013272 t7 0xfffffc000065e000 -4398039834624 s0 0x800 2048 s1 0x1201550e8 4833235176 s2 0x120146280 4833174144 s3 0x120106070 4832911472 s4 0x120146280 4833174144 s5 0x1201462c0 4833174208 fp 0x120146300 4833174272 a0 0xe 14 a1 0x0 0 a2 0x11ffaf30 301969200 a3 0x0 0 a4 0x0 0 a5 0x0 0 t8 0x0 0 t9 0x11ffbfb8 301973432 t10 0x8 8 t11 0x0 0 ra 0x11ffbfc4 301973444 t12 0xfffffc00003af9c0 -4398042646080 at 0xfffffe0003d12000 -2198959218688 gp 0x120105070 4832907376 sp 0x11ffaf18 301969176 zero 0x0 0 pc 0xfffffc00003af9c0 -4398042646080 vfp 0x0 0 (gdb) Interestingly, $t12 and $pc are both _mtx_exit and $t2 is Giant. The other high addresses are off the end of the kernel. Within ppp, $s3 is bundle.141 (bundle in bundle.c AFAIK). Apart from $gp, the other addresses are either beyond _end or before _init. $gp is between: 00000001200fd068 ? __DTOR_END__ 00000001201058c8 A __bss_start Anomolies include the discrepancy between $sp and $fp as well as $ra being less then start. Does anyone have any ideas as to the cause, or where I should start looking? The kernel addresses inside a (supposedly) userland core dump has me confused. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010219074428.E70642>