From: Elena Zannoni <ezannoni@redhat.com>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: carlton@math.stanford.edu, ezannoni@redhat.com,
gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Make tests more flexible
Date: Thu, 16 Jan 2003 17:53:00 -0000 [thread overview]
Message-ID: <15910.62083.363876.797928@localhost.redhat.com> (raw)
In-Reply-To: <200301161735.h0GHZAM15898@duracef.shout.net>
Michael Elizabeth Chastain writes:
> Ah, okay, my head is spinning with all the mail flying around.
>
> David C's log files are the same as my log files.
> It looks like one bug in both advance.exp and until.exp.
> For me:
> It happened the same way for both dwarf-2 and stabs+.
> It happened the same way with all binutils.
> It happened with gcc => 3.2.1, gcc-3_2-branch, gcc-3_3-branch, HEAD.
> It did NOT happen with gcc => 2.95.3, vendor.
>
> So I think there is only one bug here I think Elena Z can reproduce it
> by using a gcc v3 compiler with any debug format.
>
> Michael C
Ah ok, I am using gcc version 2.96 20000731 (Red Hat Linux 7.2 2.96-108.7.2).
So, recapping, which one is correct? the old compiler (and the test is
right) or the new compiler (and the test is wrong)?
Elena
next prev parent reply other threads:[~2003-01-16 17:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-16 17:35 Michael Elizabeth Chastain
2003-01-16 17:53 ` Elena Zannoni [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-16 18:45 Michael Elizabeth Chastain
2003-01-16 18:07 Michael Elizabeth Chastain
2003-01-16 17:27 Michael Elizabeth Chastain
2003-01-16 17:24 Michael Elizabeth Chastain
2003-01-16 4:36 Michael Elizabeth Chastain
2003-01-16 2:05 Elena Zannoni
2003-01-16 4:50 ` David Carlton
2003-01-16 17:19 ` Elena Zannoni
2003-01-16 14:40 ` Fernando Nasser
2003-01-16 16:40 ` Elena Zannoni
2003-01-16 17:10 ` David Carlton
2003-01-16 17:27 ` 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=15910.62083.363876.797928@localhost.redhat.com \
--to=ezannoni@redhat.com \
--cc=carlton@math.stanford.edu \
--cc=gdb-patches@sources.redhat.com \
--cc=mec@shout.net \
/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