|
From: Jeremy F. <je...@go...> - 2005-01-10 00:15:34
|
I think we're talking at cross purposes a bit.
I see it as a pretty serious limitation that you can't use gdb on a
program while it runs under Valgrind. If we implement the gdbstub
protocol, we fix this in a very satisfactory way, since its immediately
usable by anyone who has pretty much any version of gdb installed. It's
nice for us too, since the protocol is stable and self-contained, and
won't pose any maintenance headaches. It's the 95% solution.
Sure, it would be nice to get the other 5%, some way of querying Tool
state from within the debugger. That could be solved either by
proposing a new debugger interface, or by trying to squeeze more out of
the gdbstub interface (by, for example, finding some way to set
breakpoints/watchpoints which are triggered by a Tool warning message).
I think the first is really important. We can worry about the second
once the first is in place. Holding back the first 95% of the answer
just so we can get the last 5% doesn't seem like a good tradeoff.
J
|