From: Michael Elizabeth Chastain <mec@shout.net>
To: carlton@math.stanford.edu, ezannoni@redhat.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Merge of readline 4.3 to mainline
Date: Mon, 09 Dec 2002 16:27:00 -0000 [thread overview]
Message-ID: <200212092342.gB9Ngdq00487@duracef.shout.net> (raw)
Heh. I figured out what's special about my system.
I build the whole toolchain from scratch, starting with gnu make, then
binutils, then a baseline version of gcc. Then I use the baseline tools
to build everything else, including all the binutils, gcc's, and gdb's
that I test with. Then I run all the tests.
The idea of the baseline is to make a test bed that can bootstrap on
systems without the gnu toolchain, like Solaris.
My baseline compiler is gcc 2.95.3, because it's simple and fast.
When I build gdb with /bin/cc, or when I use gcc 3.2.1 + binutils 2.13.1,
the strange behavior in readline does not happen and my gdb.log looks
normal and good.
So it's some interaction with building gdb with gcc 2.95.3 and then
running on red hat linux 8 that causes the perverse line refreshes.
I figure this falls in the category of "don't do that!"
Anyways now we know a little more about readline in case the perverse
line refreshes ever strike anyone else.
Feeling bashful,
Michael C
next reply other threads:[~2002-12-09 23:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-09 16:27 Michael Elizabeth Chastain [this message]
2002-12-09 18:32 ` Elena Zannoni
-- strict thread matches above, loose matches on Subject: below --
2002-12-09 14:38 Michael Elizabeth Chastain
2002-12-09 14:09 Michael Elizabeth Chastain
2002-12-09 14:14 ` David Carlton
2002-12-09 13:42 Michael Elizabeth Chastain
2002-12-09 13:57 ` Elena Zannoni
2002-12-09 14:00 ` Elena Zannoni
2002-12-07 3:57 Elena Zannoni
2002-12-08 14:34 ` Elena Zannoni
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=200212092342.gB9Ngdq00487@duracef.shout.net \
--to=mec@shout.net \
--cc=carlton@math.stanford.edu \
--cc=ezannoni@redhat.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