Date: Thu, 05 Mar 2015 10:04:33 -0500 From: John Baldwin <jhb@freebsd.org> To: freebsd-hackers@freebsd.org Cc: Shrikanth Kamath <shrikanth07@gmail.com> Subject: Re: Glitch with textdump/ddb Message-ID: <1935444.uB8LrzP6Br@ralph.baldwin.cx> In-Reply-To: <CAEOAkMWZ-i1OWEQzX2H%2BNMkCFwGOdehRR65v2HHi-jXQrYyPrA@mail.gmail.com> References: <CAEOAkMWZ-i1OWEQzX2H%2BNMkCFwGOdehRR65v2HHi-jXQrYyPrA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday, March 04, 2015 01:06:17 AM Shrikanth Kamath wrote: > But if I change the script to > ddb script kdb.enter.panic="textdump set; capture on; show pcpu; ps; > call doadump(1)" > > The value supplied to call doadump when the machine enters debugger > on panic is now set to '1'. > > Should this be the right way to capture information when using text > dumps? I guess the man page for textdump specifies just "call > doadump". The problem may not manifest as long the random value picked > off the stack is non zero. Yes, the value should be passed explicitly. HEAD now has a 'dump' command that is preferred to calling doadump directly though. (Not sure if that command has been merged to any stable branches.) -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1935444.uB8LrzP6Br>