From: Daniel Jacobowitz <drow@false.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA/DWARF] variables with no DW_AT_location
Date: Thu, 29 Mar 2007 18:56:00 -0000 [thread overview]
Message-ID: <20070329185602.GF28418@caradoc.them.org> (raw)
In-Reply-To: <20070329184244.GB3737@adacore.com>
On Thu, Mar 29, 2007 at 11:42:44AM -0700, Joel Brobecker wrote:
> > Is this patch coming from an older tree? Because dwarf2read doesn't
> > do that any more.
>
> Argh!!! Certain files in my tree had weird tags, and I have no idea
> why. I made a clean check out of the sources, and now I see:
>
> Address of symbol "noloc" is unknown.
>
> Thanks for catching this, and sorry for the trouble.
> Should we still keep the testcase, though? (revised)
>
> 2007-03-29 Joel Brobecker <brobecker@adacore.com>
>
> * gdb.dwarf2/dw2-noloc.S: New file.
> * gdb.dwarf2/dw2-noloc.exp: New file.
OK, thanks.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-03-29 18:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-28 22:21 Joel Brobecker
2007-03-29 2:20 ` Daniel Jacobowitz
2007-03-29 18:41 ` Joel Brobecker
2007-03-29 18:56 ` Daniel Jacobowitz [this message]
2007-03-29 19:31 ` Joel Brobecker
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=20070329185602.GF28418@caradoc.them.org \
--to=drow@false.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
/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