From: Daniel Jacobowitz <drow@mvista.com>
To: Eli Zaretskii <eliz@elta.co.il>
Cc: Andrew Cagney <cagney@gnu.org>, gdb@sources.redhat.com
Subject: Re: GCC 3.4 vs GDB 6.1
Date: Fri, 09 Jan 2004 14:36:00 -0000 [thread overview]
Message-ID: <20040109143618.GA32690@nevyn.them.org> (raw)
In-Reply-To: <6654-Fri09Jan2004105457+0200-eliz@elta.co.il>
On Fri, Jan 09, 2004 at 10:54:57AM +0200, Eli Zaretskii wrote:
> > Date: Thu, 08 Jan 2004 15:30:58 -0500
> > From: Andrew Cagney <cagney@gnu.org>
> >
> > (kind of a bit late but ...)
> > Are there any "bugs" GDB would like to see fixed in GCC 3.4?
>
> How about this thingy:
>
> http://sources.redhat.com/ml/gdb/2003-12/msg00271.html
>
> Does it sound like a GCC bug?
No idea without more information. Did you ever get dwarfdump to work
on COFF?
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2004-01-09 14:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-08 20:30 Andrew Cagney
2004-01-08 20:33 ` Daniel Jacobowitz
2004-01-09 8:57 ` Eli Zaretskii
2004-01-09 14:36 ` Daniel Jacobowitz [this message]
2004-01-10 11:54 ` Eli Zaretskii
2004-01-10 16:34 ` Daniel Jacobowitz
2004-01-08 21:24 Michael Elizabeth Chastain
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=20040109143618.GA32690@nevyn.them.org \
--to=drow@mvista.com \
--cc=cagney@gnu.org \
--cc=eliz@elta.co.il \
--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