This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: Can symbol-reading produce terminal output?
- From: Pedro Alves <pedro at codesourcery dot com>
- To: gdb-patches at sourceware dot org
- Cc: Joel Brobecker <brobecker at adacore dot com>, Eli Zaretskii <eliz at gnu dot org>
- Date: Mon, 11 May 2009 11:25:55 +0100
- Subject: Re: Can symbol-reading produce terminal output?
- References: <83tz3ubd0h.fsf@gnu.org> <20090511101114.GC14773@adacore.com>
On Monday 11 May 2009 11:11:14, Joel Brobecker wrote:
> If we were doing things in a more systematic way, I'd say that this
> call belongs in the code that handles kernel events. The terminal
> should be the inferior's when we're waiting for events, and it should
> be ours when we're no longer waiting (either processing an event, or
> waiting for the next user command). That reminds me, though: What do
> we do when we're in non-stop mode???
s/non-stop/async/. See linux_nat_terminal_inferior, and remote_terminal_inferior.
Basically, if executing in the background, GDB stays with the terminal;
If executing in the foreground, the inferior gets the terminal.
The interesting question, is what happens with multi-process... Currently, I'm
just ignoring that problem. If two programs want to fight for the terminal,
then if you want to debug them simultaneously, you should attach to
them anyway.
--
Pedro Alves