From: "Mike Frysinger" <vapier@gmail.com>
To: "Mike Frysinger" <vapier@gentoo.org>,
"Mike Frysinger" <vapier@gmail.com>,
gdb-patches@sourceware.org
Subject: Re: [patch] early abort if child spawning failed
Date: Sat, 22 Sep 2007 04:18:00 -0000 [thread overview]
Message-ID: <ba49ee420709212118x6cbd5496iafd371c7266b0662@mail.gmail.com> (raw)
In-Reply-To: <20070922035842.GA10326@caradoc.them.org>
On 9/21/07, Daniel Jacobowitz <drow@false.org> wrote:
> On Fri, Sep 21, 2007 at 10:31:11PM -0400, Mike Frysinger wrote:
> > if you use gdbserver to listen on a port and the specified program fails to
> > launch properly, the server process will continue on to the accept() call and
> > sit there forever ... you cant control+c the process as the signals are taken
> > over which means you have to connect with gdb to force the server to re-check
> > itself and then abort ... all in all, a pita for a simple typo.
> >
> > the attached patch checks the status field immediately after launch rather
> > than falling down into the main loop and waiting for the remote debugger to
> > connect for the status to get properly checked.
>
> Did you port this from an earlier version?
yep
> It shouldn't be necessary any more - Michael fixed this 2007-07-27.
when i looked at the CVS HEAD version, the comment "we assume success"
led me to believe that the situation was unchanged ... but looking at
the diff, the patch i proposed is pretty much the same as the one
Michael proposed so yeah, what i posted can just be dropped ...
thanks
-mike
prev parent reply other threads:[~2007-09-22 4:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-22 2:31 Mike Frysinger
2007-09-22 3:58 ` Daniel Jacobowitz
2007-09-22 4:18 ` Mike Frysinger [this message]
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=ba49ee420709212118x6cbd5496iafd371c7266b0662@mail.gmail.com \
--to=vapier@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=vapier@gentoo.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