From: Michael Elizabeth Chastain <chastain@cygnus.com>
To: chastain@cygnus.com, msnyder@redhat.com
Cc: gdb-patches@sources.redhat.com, jmoore@cygnus.com
Subject: Re: [RFA] Fix for gdb-gnats bug #14
Date: Sun, 18 Feb 2001 15:57:00 -0000 [thread overview]
Message-ID: <200102182357.PAA20575@bosch.cygnus.com> (raw)
Hi Michael,
> No. Trust me -- it never did. This would require infrastructure
> that has never existed, and would require code to be reentrant which
> has always relied on global variables.
OK, that part of my speculation is wrong.
So it looks like the original author of commands.exp suffered from the
same error. The original author probably thought gdb was broken, but
actually the test case was broken at birth.
Michael
next reply other threads:[~2001-02-18 15:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-18 15:57 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-02-16 17:54 Michael Elizabeth Chastain
2001-02-16 17:19 Michael Elizabeth Chastain
2001-02-16 17:36 ` Michael Snyder
[not found] <200102170027.QAA01551@bosch.cygnus.com>
2001-02-16 16:44 ` John R. Moore
2001-02-16 13:44 Michael Elizabeth Chastain
2001-02-16 13:56 ` John R. Moore
2001-02-16 10:04 John R. Moore
2001-02-16 14:40 ` John R. Moore
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=200102182357.PAA20575@bosch.cygnus.com \
--to=chastain@cygnus.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jmoore@cygnus.com \
--cc=msnyder@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