From: Andrew Cagney <ac131313@cygnus.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa] gdbserver signal handling
Date: Thu, 28 Feb 2002 12:55:00 -0000 [thread overview]
Message-ID: <3C7E9932.4090803@cygnus.com> (raw)
In-Reply-To: <20020228153023.A16149@nevyn.them.org>
> Yes. It isn't as bad as it sounds though. The problem has always been
>> there so we're not exactly fixing a regression. Besides, the next
>> release is only 22 weeks away.
>
>
> My motivation to finish this before release was that this was the only
> remaining set of tests which gdbserver should have been able to pass
> and could not after my rewrite; it'll be built on a lot more platforms
> now, and probably used more. It didn't pass particularly many of
> them beforehand. This isn't terribly important to me, since I'm only
> responsible for two distributions of GDB and both of them have patch
> application mechanisms (:-)), but I suspect we'll see it reported
> pretty frequently over the next 22 weeks.
I'm more worred by the far too frequent ``gdbserver isn't built''
e-mail. If someone sends a bug report indicating a problem in
gdbserver's signal handling (indicating they managed to build
gdbserver), I'll be breaking out the bubbly! :-)
> I agree that the patch isn't ideal; but if a proper fix goes in the
> mainline can we put this on the branch?
I'll leave that decision to when the proper fix is in the trunk.
Andrew
prev parent reply other threads:[~2002-02-28 20:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-27 20:12 Daniel Jacobowitz
2002-02-28 7:01 ` Andrew Cagney
2002-02-28 8:55 ` Daniel Jacobowitz
2002-02-28 9:25 ` Andrew Cagney
2002-02-28 9:43 ` Daniel Jacobowitz
2002-02-28 11:29 ` Andrew Cagney
2002-02-28 12:30 ` Daniel Jacobowitz
2002-02-28 12:55 ` Andrew Cagney [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=3C7E9932.4090803@cygnus.com \
--to=ac131313@cygnus.com \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.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