From: Daniel Jacobowitz <drow@false.org>
To: Pierre Muller <muller@ics.u-strasbg.fr>
Cc: Andreas Schwab <schwab@suse.de>, gdb-patches@sourceware.org
Subject: Re: Testsuite failures in gdb.dwarf2/{dup-psym,mac-fileno}.exp
Date: Fri, 02 Feb 2007 11:41:00 -0000 [thread overview]
Message-ID: <20070202114056.GA15202@nevyn.them.org> (raw)
In-Reply-To: <2674.130.79.112.72.1170412166.squirrel@www-ics.u-strasbg.fr>
On Fri, Feb 02, 2007 at 11:29:26AM +0100, Pierre Muller wrote:
> On Wed, January 31, 2007 17:43, Andreas Schwab said:
> > There are two other testcases with invalid DWARF sections. Checked in
> as
> > obvious.
>
> I was just wandering if this would also be correct
> on a chip that a 64bit memory addresses.
>
> Does dwarf not support these cpus?
No, it's correct. There are two DWARF-2 binary formats, one 32-bit and
the other 64-bit. But you do not need to use the 64-bit format just
because you have a 64-bit CPU - you only need to use it if you have
more than 2GB or so of debug information.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2007-02-02 11:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-31 16:43 Andreas Schwab
2007-02-02 10:32 ` Pierre Muller
2007-02-02 11:41 ` Daniel Jacobowitz [this message]
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=20070202114056.GA15202@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=muller@ics.u-strasbg.fr \
--cc=schwab@suse.de \
/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