Re: tracing, attaching to gdb processes

[Daniel Jacobowitz <drow@false.org>]

On Tue, Mar 14, 2006 at 08:16:18PM -0800, Ed Peschko wrote:
> Also, I note that when you do do something like this, you get a 'press <return> to
> coninue, q<return> to quit'. It would be nice if there was a way to override this.

"set height 0"

Stopping on input is a bit more complicated than you think.  Whenever
the program is running, it has control of the terminal - and input goes
to it, not to us.  I don't see an easy way to do this.

> well, cool.. then simply add that as a hook inside the library. Which would 
> you rather write (continuously), the first one, or the second? And isn't it useful
> to have it just for suggesting ideas to end users of gdb?

That says to me that it belongs in the manual.  Shipping a library is a
serious pain; why should we do it for a two-line function?

> Anyways, if this isn't the place to request gdb features, what *is* the correct
> place?

It's the right place; I'm just not sure I agree with your suggestions.
If someone else does, they're welcome to submit a patch :-)

-- 
Daniel Jacobowitz
CodeSourcery