From: "Doug Evans" <dje@google.com>
To: gdb-patches@sourceware.org
Subject: Re: [RFC] gdb could leave inferior running as a background process
Date: Wed, 23 Apr 2008 02:19:00 -0000 [thread overview]
Message-ID: <e394668d0804221508r7b4e3a64k8e57d833ba57fe9b@mail.gmail.com> (raw)
In-Reply-To: <20080422203926.GA31285@caradoc.them.org>
On Tue, Apr 22, 2008 at 1:39 PM, Daniel Jacobowitz <drow@false.org> wrote:
> On Tue, Apr 22, 2008 at 01:36:01PM -0700, Doug Evans wrote:
> > It seems like there are multiple places where this can happen. E.g.
> > wait_for_inferior -> handle_inferior_event -> find_pc_partial_function
> > -> target_terminal_ours_for_output.
>
> But by then it's stopped, right? As long as something makes sure we
> give the terminal back after the warning it shouldn't be a problem.
Ah. It's hard to reason about correctness in this part of gdb. I can
see that keep_going calls target_terminal_inferior, but the code paths
are embedded in a big hairy state machine. [I've seen what
wait_for_inferior used to be, things *have* improved though.]
next prev parent reply other threads:[~2008-04-22 22:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-22 16:12 Paul Pluzhnikov
2008-04-22 17:40 ` Daniel Jacobowitz
2008-04-22 17:56 ` Paul Pluzhnikov
2008-04-22 18:05 ` Paul Pluzhnikov
2008-04-22 19:55 ` Daniel Jacobowitz
2008-04-22 20:29 ` Paul Pluzhnikov
[not found] ` <20080422195515.GA28506@caradoc.them.org>
2008-04-22 21:35 ` Doug Evans
2008-04-22 22:09 ` Daniel Jacobowitz
2008-04-23 2:19 ` Doug Evans [this message]
2008-04-23 3:54 ` Daniel Jacobowitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e394668d0804221508r7b4e3a64k8e57d833ba57fe9b@mail.gmail.com \
--to=dje@google.com \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox