From: David Anderson <davea@quasar.engr.sgi.com>
To: eliz@elta.co.il
Cc: gdb@sources.redhat.com, drow@mvista.com
Subject: Re: inner block not inside outer block
Date: Tue, 30 Dec 2003 18:01:00 -0000 [thread overview]
Message-ID: <200312301757.hBUHvMPN067891@quasar.engr.sgi.com> (raw)
|
|> Date: Sun, 28 Dec 2003 13:46:56 -0500
|> From: Daniel Jacobowitz <drow@mvista.com>
|>
|> You can't use readelf but I assume you can get one of
|> the other DWARF debugging tools to work - maybe dwarfdump - and figure
|> out what the actual bounds of the blocks in question are?
From:"Eli Zaretskii" <eliz@elta.co.il>
|I tried dwarfdump (the version from 29-Aug-2001), but couldn't build
|it, not even on Debian GNU/Linux: it chokes on the missing definition
|of the `Elf' data type. How did you manage to build it? Is there
There was one release with a botch in the #include stuff, which
lead to a build error on linux.
The current version is libdwarf20031006.tar.gz
|perhaps a newer version that is better? (I tried to google for it and
|found a pointer to Dave Anderson's page where there's supposed to be a
|version from this year, but that page seems to be unreachable.)
reality.sgiweb.org went down Monday at 6:30 or so Pacific Time.
As of 10AM Pacific Time it seems to be back up.
If you still have problems building, let me know the details
as I do want it to build correctly!
David Anderson
next reply other threads:[~2003-12-30 18:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-30 18:01 David Anderson [this message]
2003-12-30 23:04 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2003-12-28 11:24 Eli Zaretskii
2003-12-28 18:46 ` Daniel Jacobowitz
2003-12-30 14:42 ` Eli Zaretskii
2003-12-30 15:27 ` Daniel Jacobowitz
2003-12-31 3:36 ` Daniel Berlin
2003-12-29 14:54 ` Paul Koning
2003-12-29 15:38 ` Eli Zaretskii
2003-12-29 16:06 ` Daniel Jacobowitz
2003-12-29 21:54 ` Eli Zaretskii
2003-12-29 16:17 ` Paul Koning
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=200312301757.hBUHvMPN067891@quasar.engr.sgi.com \
--to=davea@quasar.engr.sgi.com \
--cc=drow@mvista.com \
--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