From: Daniel Jacobowitz <drow@false.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Greg Law <glaw@undo-software.com>, gdb-patches@sourceware.org
Subject: Re: gdb-6.8 branchpoint
Date: Wed, 27 Feb 2008 02:55:00 -0000 [thread overview]
Message-ID: <20080227010757.GA26947@caradoc.them.org> (raw)
In-Reply-To: <20080226223023.GB5326@adacore.com>
On Tue, Feb 26, 2008 at 02:30:23PM -0800, Joel Brobecker wrote:
> > As per earlier on-list discussion, any chance of applying this simple
> > fix to prevent random SEGV's in gdb?
>
> Yes, this can go in the branch on the condition that it is approved
> by a Global Maintainer for HEAD first.
Now done.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2008-02-27 1:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-26 21:54 Joel Brobecker
2008-02-26 21:57 ` Thiago Jung Bauermann
2008-02-26 22:25 ` Daniel Jacobowitz
2008-02-26 22:26 ` Thiago Jung Bauermann
2008-02-26 22:30 ` Joel Brobecker
2008-02-26 22:02 ` Greg Law
2008-02-26 22:37 ` Joel Brobecker
2008-02-27 0:26 ` Michael Snyder
2008-02-27 2:55 ` Daniel Jacobowitz [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=20080227010757.GA26947@caradoc.them.org \
--to=drow@false.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=glaw@undo-software.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