From: Daniel Jacobowitz <drow@false.org>
To: Andreas Schwab <schwab@suse.de>,
Ulrich Weigand <uweigand@de.ibm.com>,
gdb-patches@sourceware.org, bash-maintainers@gnu.org
Subject: Re: [PATCH] Readline bug causes GDB crash on 64-bit
Date: Fri, 20 Oct 2006 21:36:00 -0000 [thread overview]
Message-ID: <20061020213559.GB14966@nevyn.them.org> (raw)
In-Reply-To: <20061020213228.GA14966@nevyn.them.org> <jey7rar7yw.fsf@sykes.suse.de>
Oops, didn't see Andreas's reply before I sent mine...
On Fri, Oct 20, 2006 at 11:30:15PM +0200, Andreas Schwab wrote:
> "Ulrich Weigand" <uweigand@de.ibm.com> writes:
>
> > What's the policy for readline bugs in GDB? It is OK to check
> > this patch into GDB, or does it have to go upstream first?
>
> Upstream does not have this bug any more.
I guess we ought to import readline 5.2 sometime.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-10-20 21:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-20 21:10 Ulrich Weigand
2006-10-20 21:30 ` Andreas Schwab
2006-10-20 21:36 ` Daniel Jacobowitz [this message]
2006-10-20 21:32 ` Daniel Jacobowitz
2006-10-21 2:56 ` Chet Ramey
2006-10-21 5:15 ` Daniel Jacobowitz
2006-10-21 20:48 ` Ulrich Weigand
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=20061020213559.GB14966@nevyn.them.org \
--to=drow@false.org \
--cc=bash-maintainers@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=schwab@suse.de \
--cc=uweigand@de.ibm.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