On 15-May-2002 Dag-Erling Smorgrav wrote: > John Baldwin <[EMAIL PROTECTED]> writes: >> The kernel overflowed it's stack. In SRM, you can try to debug this >> by using 'e sp' to get the stack pointer then get a stack dump and save >> a copy of it in a log or something, reboot the machine, then use gdb's >> list command on the kernel.debug to figure out the source:line for all >> the kernel-text addresses in the stack dump to figure out the backtrace. > > How do I get a stack trace? I can't get the 'examine' command to > actually print anything...
It depends on which machine actually. :-/ First do 'e sp' to get the stack pointer. Then you want to do something like this: e -n 100 <value of sp without any leading 0x> if that doesn't work then try: e -n 100 vmem:<value of sp w/o leading 0x> This should basically do a raw memory dump. However, see if phk's daddr_t reversal fixes it first. -- John Baldwin <[EMAIL PROTECTED]> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
