Re: kdb_read not exported

To:	"Grover, Andrew" <andrew.grover@xxxxxxxxx>
Subject:	Re: kdb_read not exported
From:	Keith Owens <kaos@xxxxxxxxxxxxxxxxx>
Date:	Thu, 21 Sep 2000 17:04:56 +1100
Cc:	"'kdb@xxxxxxxxxxx'" <kdb@xxxxxxxxxxx>
In-reply-to:	Your message of "Wed, 20 Sep 2000 22:32:01 PDT." <4148FEAAD879D311AC5700A0C969E8905DE367@xxxxxxxxxxxxxxxxxxxxx>
Sender:	owner-kdb@xxxxxxxxxxx

On Wed, 20 Sep 2000 22:32:01 -0700, 
"Grover, Andrew" <andrew.grover@xxxxxxxxx> wrote:
>I'm writing a module for kdb.
>
>I would find kdb_read's functionality useful in my module. If I export and
>use it, will anything break?

kdb v1.5 (out soon) is a major redesign of the cpu state handling, to
get finer grained control over single step and recovery from oopsing or
hung kdb commands.  Part of that redesign affects the way kdb_read()
works, especially the longjmp() to break out of a command.  Ask me
again after v1.5 is out.

<Prev in Thread]	Current Thread	[Next in Thread>
kdb_read not exported, Grover, Andrew Re: kdb_read not exported, Keith Owens <=

Previous by Date:	RE: Source level debugging with kdb, Grover, Andrew
Next by Date:	Re: Source level debugging with kdb, Keith Owens
Previous by Thread:	kdb_read not exported, Grover, Andrew
Next by Thread:	KDB Compile problems, Anmol Sheth
Indexes:	[Date] [Thread] [Top] [All Lists]