kdb_read not exported

[Grover, Andrew]

Hi Keith,

I was happy to see the 1.5 release announcement this morning. Wow, that was
quick. ;-) Based on that, is it possible to say whether a module's use of
kdb_read is okay now?

Regards -- Andy

-----Original Message-----
From: Keith Owens [mailto:kaos at melbourne.sgi.com]
Sent: Wednesday, September 20, 2000 11:05 PM
To: Grover, Andrew
Cc: 'kdb at oss.sgi.com'
Subject: Re: kdb_read not exported 


On Wed, 20 Sep 2000 22:32:01 -0700, 
"Grover, Andrew" <andrew.grover at intel.com> 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.