Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: tromey@redhat.com
Cc: brobecker@adacore.com, gdb-patches@sourceware.org
Subject: Re: DWARF-related warnings in DJGPP build of GDB
Date: Wed, 15 Apr 2009 20:17:00 -0000	[thread overview]
Message-ID: <83iql5llja.fsf@gnu.org> (raw)
In-Reply-To: <m3fxg9g0m6.fsf@fleche.redhat.com>

> Cc: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sourceware.org
> From: Tom Tromey <tromey@redhat.com>
> Date: Wed, 15 Apr 2009 13:47:45 -0600
> 
> >>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:
> 
> Pedro> You could try dumping the DWARF data if you have a tool that does that
> Pedro> on your system.
> 
> Eli> What tools can do that?  Is there a way of doing this with Binutils?
> 
> You can use objdump -W or readelf -w (if DJGPP uses ELF) to dump debug
> info.

Thanks.  readelf is out, because DJGPP uses COFF.  "objdump -W" (with
a recent enough Binutils ;-) seems to do the job, thanks.  How to use
the info it dumps on me to track down my particular problems is
another matter.  Hmmm...


  reply	other threads:[~2009-04-15 20:17 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
2009-04-15 21:00         ` Pedro Alves
2009-04-15 19:48     ` Tom Tromey
2009-04-15 20:17       ` Eli Zaretskii [this message]
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=83iql5llja.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@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