Date: Sat, 30 Jul 2011 11:14:34 +0300 From: Andriy Gapon <avg@FreeBSD.org> To: maestro something <maestro82@gmail.com> Cc: freebsd-stable@FreeBSD.org Subject: Re: dtrace ustack kernel panic Message-ID: <4E33BD6A.4030303@FreeBSD.org> In-Reply-To: <4E33B7CF.90200@FreeBSD.org> References: <CAJ_JOqvEmXBTBABhUcJ66=bh9%2B8S%2BC9v30hXxVZiCXuEpGPJ1A@mail.gmail.com> <4E2E9F60.1060808@FreeBSD.org> <CAJ_JOqszViwLi6TeQxAxeX2Mte5eBPsGJpjQPVOQs2BOwAq9JQ@mail.gmail.com> <4E33B7CF.90200@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
on 30/07/2011 00:27 maestro something said the following: > on 30/07/2011 10:50 Andriy Gapon said the following: >> #7 0xc11012d7 in dtrace_panic_trigger () from /boot/kernel/dtrace.ko >> > Previous frame inner to this frame (corrupt stack?) >> > (kgdb) >> > >> > what am I doing wrong and what do I have to do to get the specific assert that >> > fails? > I am not quite sure. Apparently there is some issue with either what > information we store in a crash dump and how, or with how kgdb interprets that > information, or with a combination of both... Or maybe it's because dtrace_panic_trigger is a function implemented in assembly and we do not provide enough debug information to (k)gdb in that case. -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4E33BD6A.4030303>