On Sat, Jan 28, 2006 at 11:39:27AM +0000, Darren Reed wrote:
> On Sat, Jan 28, 2006 at 12:19:42PM +0100, Manuel Bouyer wrote:
> > On Sat, Jan 28, 2006 at 09:52:45AM +0000, Darren Reed wrote:
> > > > ddb.commandonenter is not enough?
> > > 
> > > That doesn't exist.
> > 
> > >From -current ddb(4):
> >      To specify commands which will be executed on each entry to ddb:
> >      options DDB_COMMANDONENTER="trace;show registers"
> >      In this case, "trace" and then "show registers" will be executed automat-
> >      ically.
> > 
> > So just use options DDB_COMMANDONENTER="trace" in your kernel config
> > file and you get the same functionality. Or ddb.commandonenter=trace
> > in /etc/sysctl.conf
> 
> This also needs to be documented in options(4) and panic(9) as well
> as wherever else is necessary.

Others DDB options are in options(4) so this one should as well, I'll fix
this. I don't think it has its place in panic(9) though.

> 
> However I'm not convinced this will do what I want as ddb fails to
> do anything except print the panic message for me.

It did for me on Xen, before I had a complete console driver, or
if the panic occurs before the console is fully initialized.
Don't you get a ddb> prompt ? If so it should work.


-- 
Manuel Bouyer <bouyer@antioche.eu.org>
     NetBSD: 26 ans d'experience feront toujours la difference
--