Date: Fri, 12 Jan 2001 16:45:41 +0200 (EET) From: diman <diman@asd-g.com> To: Xavier Galleri <xgalleri@enition.com> Cc: Alfred Perlstein <bright@wintelcom.net>, freebsd-hackers@FreeBSD.ORG Subject: Re: Need help for kernel crash dump analysis Message-ID: <Pine.BSF.4.21.0101121619441.320-100000@portal.none.ua> In-Reply-To: <3A5ED923.3010207@enition.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 12 Jan 2001, Xavier Galleri wrote: > OK, let's make it a bit clearer ! ... [skiped] > > Now, if you've read my first mail, I was actually asking for help onhow > to dump the stack of an interrupted process with GDB when the > kernelcrash occurs in the context of an isr. Actually, I would like to > know how I could dump the stack of *any* process at the time of the > crash. This way, I would be able to see where my user-land daemon was > lying in the kernel when the interrupt occurs. To dump stack of *any* (all) process you may write a little kld wich will: 1) go through a process list, 2) get tf_eip, tf_esp, tf_ebp of a process 3) get p->p_vmspace 4) read process stack frames and all you need by manually written routine based on procfs_rwmem and old good 'pread' (which dosn't work now) Another way is to go through proc list and coredump all the processes for future manual analisys. I like such way. Can anybody point me to some difficults wich can appear while implementing this? > [skiped] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0101121619441.320-100000>