Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Paul Pluzhnikov <ppluzhnikov@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] gdb could leave inferior running as a background process
Date: Tue, 22 Apr 2008 19:55:00 -0000	[thread overview]
Message-ID: <20080422180459.GB20664@caradoc.them.org> (raw)
In-Reply-To: <8ac60eac0804221051p6ad56743g202a6f920d1c6315@mail.gmail.com>

On Tue, Apr 22, 2008 at 10:51:29AM -0700, Paul Pluzhnikov wrote:
> On Tue, Apr 22, 2008 at 9:46 AM, Paul Pluzhnikov <ppluzhnikov@google.com> wrote:
> 
> >  Would attached patch work better then?
> 
> Actually, the second patch doesn't fix the problem by itself:
> inferior is resumed, then warning is issued, then we block.
> 
> So both the first and second patches are needed.

Any time the second patch is "needed", there's still a race condition
and the bug is present.  We're running in parallel with the inferior
at this point.

Where is the warning issued?

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2008-04-22 18:05 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 [this message]
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
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=20080422180459.GB20664@caradoc.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=ppluzhnikov@google.com \
    /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