From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org, brobecker@adacore.com
Subject: Re: DWARF-related warnings in DJGPP build of GDB
Date: Wed, 15 Apr 2009 20:48:00 -0000 [thread overview]
Message-ID: <83d4bdlk2h.fsf@gnu.org> (raw)
In-Reply-To: <200904152031.20517.pedro@codesourcery.com>
> From: Pedro Alves <pedro@codesourcery.com>
> Date: Wed, 15 Apr 2009 20:31:19 +0100
> Cc: Joel Brobecker <brobecker@adacore.com>
>
> On Wednesday 15 April 2009 20:26:37, Eli Zaretskii wrote:
> > > It could be the compiler emitting wrong debugging info, or the
> > > assembler/linker toolchain that screws up.
> >
> > I will try to upgrade to newer Binutils and to GCC 3.4.4, and see if
> > that helps.
> ^^^^^
>
> Interesting, is there a reason to stay with the gcc 3 series on DJGPP?
I'm very conservative in upgrading my development tools. As long as
something works fine for me, I'm reluctant to do significant upgrades,
because doing so runs a risk of destabilizing the development
environment, and with so little free time, I cannot afford that,
unless strictly necessary.
> I was using DJGPP gcc 4.2.3 last time I tried DJGPP (it's on the wiki),
> and it was a prebuilt binary.
A DJGPP port of GCC 4.3.2 is available since Sep 2008, but I dislike
GCC 4.x because it whines too much about perfectly valid C code. (It
may not be a problem with GDB sources, but I compile other projects
besides GDB.) So, if GCC 3.4.4 solves the problems I have, I won't
have a significant incentive to go to 4.x.
> I don't remember if I saw those dwarf issues. May be worth giving
> that a shot too.
If 3.x won't help, then I might do just that.
Thanks.
next prev parent reply other threads:[~2009-04-15 20:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-15 10:10 Eli Zaretskii
2009-04-15 16:22 ` Joel Brobecker
2009-04-15 19:26 ` Eli Zaretskii
2009-04-15 19:31 ` Pedro Alves
2009-04-15 20:48 ` Eli Zaretskii [this message]
2009-04-15 21:00 ` Pedro Alves
2009-04-15 19:48 ` Tom Tromey
2009-04-15 20:17 ` Eli Zaretskii
2009-04-15 22:29 ` Joel Brobecker
2009-04-17 9:40 ` Eli Zaretskii
2009-04-17 10:11 ` Mark Kettenis
2009-04-17 10:19 ` Eli Zaretskii
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=83d4bdlk2h.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.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