From: Daniel Jacobowitz <drow@mvista.com>
To: gdb@sources.redhat.com
Subject: Re: gdb 5.3 versus gdb HEAD%200302015
Date: Mon, 17 Feb 2003 15:39:00 -0000 [thread overview]
Message-ID: <20030217153924.GA16472@nevyn.them.org> (raw)
In-Reply-To: <200302170332.h1H3WYo00673@duracef.shout.net>
On Sun, Feb 16, 2003 at 09:32:34PM -0600, Michael Elizabeth Chastain wrote:
> . gdb.mi/gdb701.exp: create fooPtr
>
> Needs investigation.
Ooh ooh. I got this one. The test is new in HEAD (wasn't in 5.3);
it's a GCC bug; it will be fixed in 3.3, 3.4, and 3.2.3 if any. I
checked the patch in the day after 3.2.2.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-02-17 15:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-17 15:32 Michael Elizabeth Chastain
2003-02-17 15:39 ` Daniel Jacobowitz [this message]
2003-02-17 17:03 ` David Carlton
2003-02-18 14:59 ` Michal Ludvig
2003-02-17 16:32 Michael Elizabeth Chastain
2003-02-17 16:35 ` Daniel Jacobowitz
2003-02-17 16:44 Michael Elizabeth Chastain
2003-02-17 16:50 ` Daniel Jacobowitz
2003-02-17 17:02 Michael Elizabeth Chastain
2003-02-17 17:08 Michael Elizabeth Chastain
2003-02-17 17:13 ` David Carlton
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=20030217153924.GA16472@nevyn.them.org \
--to=drow@mvista.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).