From: Andreas Schwab <schwab@suse.de>
To: "Ulrich Weigand" <uweigand@de.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Readline bug causes GDB crash on 64-bit
Date: Fri, 20 Oct 2006 21:30:00 -0000 [thread overview]
Message-ID: <jey7rar7yw.fsf@sykes.suse.de> (raw)
In-Reply-To: <200610202110.k9KLAiFL002481@d12av02.megacenter.de.ibm.com> (Ulrich Weigand's message of "Fri, 20 Oct 2006 23:10:43 +0200 (CEST)")
"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.
> (Where is readline upstream?)
bash
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2006-10-20 21:30 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 [this message]
2006-10-20 21:36 ` Daniel Jacobowitz
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=jey7rar7yw.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=gdb-patches@sourceware.org \
--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