From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: daniel.micol@unix.net
Cc: ezannoni@redhat.com, gdb@sources.redhat.com
Subject: Re: gdb segmentation fault
Date: Tue, 27 Jan 2004 07:25:00 -0000 [thread overview]
Message-ID: <20040127072501.1CD694B363@berman.michael-chastain.com> (raw)
Hello,
Thanks for the typescript.
This looks like it may be fixed by some new readline patches
which Elena Zannoni is about to commit. If possible, would you
be willing to apply these patches to your copy of gdb 6.0,
rebuild gdb 6.0, and try the problem again?
The patches are at:
http://sources.redhat.com/ml/gdb-patches/2004-01/msg00675.html
Thanks,
Michael C
GDB QA Guy
next reply other threads:[~2004-01-27 7:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-27 7:25 Michael Elizabeth Chastain [this message]
[not found] <20040114093241.92DB64B104@berman.michael-chastain.com>
2004-01-14 16:46 ` Daniel Micol Ponce
2004-01-15 14:50 ` Daniel Jacobowitz
-- strict thread matches above, loose matches on Subject: below --
1998-06-22 6:35 GDB " Konrad Bernloehr
1998-06-29 2:23 ` Peter.Schauer
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=20040127072501.1CD694B363@berman.michael-chastain.com \
--to=mec.gnu@mindspring.com \
--cc=daniel.micol@unix.net \
--cc=ezannoni@redhat.com \
--cc=gdb@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