kdb
[Top] [All Lists]

Re: KDB enhancements

To: Keith Owens <kaos@xxxxxxx>
Subject: Re: KDB enhancements
From: linas@xxxxxxxxxxxxxx
Date: Mon, 21 Jul 2003 11:13:18 -0500
Cc: Steven Dake <sdake@xxxxxxxxxx>, Will Schmidt <willschm@xxxxxxxxxx>, kdb@xxxxxxxxxxx
In-reply-to: <14281.1058578692@xxxxxxxxxxxxxxxxxxxxx>; from kaos@xxxxxxx on Sat, Jul 19, 2003 at 11:38:12AM +1000
References: <20030718200941.A41118@xxxxxxxxxxxxxxxxxxxx> <14281.1058578692@xxxxxxxxxxxxxxxxxxxxx>
Sender: kdb-bounce@xxxxxxxxxxx
User-agent: Mutt/1.2.5.1i
On Sat, Jul 19, 2003 at 11:38:12AM +1000, Keith Owens wrote:
> On Fri, 18 Jul 2003 20:09:41 -0500, 
> linas@xxxxxxxxxxxxxx wrote:
> >Uhh... well, kgdb does have all this stuff for crawling through stabs,
> >and symbol tables and etc.  So if source debug is really the requirement
> >then I'd think that adding the missing features to kgdb would be the 
> >simpler route.  Am I wrong?
> 
> See skdb.c in an earlier post. It works (for given values of "works")
> and lets you use gdb on a second machine into kdb instead of kgdb.  The
> biggest problem was reliably connecting to a kernel that had already
> entered kdb.

Hmm. I presume some good handshaking protocol would solve the connection
problem, right?

 
What are the philosophical distinctions between kdb and kgdb?  
Alternately: why is it a better idea to add gdb to kdb instead 
of kdb features to kgdb?

--linas

<Prev in Thread] Current Thread [Next in Thread>