From: Michael Eager <eager@eagerm.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb@sourceware.org
Subject: Re: Copy-Relocate debug error
Date: Tue, 31 Jan 2012 16:41:00 -0000 [thread overview]
Message-ID: <4F2819A0.1000003@eagerm.com> (raw)
In-Reply-To: <20120131134826.GA29517@host2.jankratochvil.net>
On 01/31/2012 05:48 AM, Jan Kratochvil wrote:
> On Mon, 30 Jan 2012 21:07:45 +0100, Michael Eager wrote:
>> Any other suggestions?
>
> This is:
> common/.bss variables from shared libraries not displayed correctly
> http://sourceware.org/bugzilla/show_bug.cgi?id=11717
Thanks. This problem isn't limited to .bss, it also happens with
initialized definitions.
> The possibilities how to fix it were discussed at:
> gfortran invalid DW_AT_location for overridable variables
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40040
Thanks again. Using DW_AT_MIPS_linkage_name or omitting the
DW_AT_location seems to be heading in the wrong direction.
I'll add notes to the bug reports.
--
Michael Eager eager@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306 650-325-8077
prev parent reply other threads:[~2012-01-31 16:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-30 20:08 Michael Eager
2012-01-31 13:48 ` Jan Kratochvil
2012-01-31 16:41 ` Michael Eager [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=4F2819A0.1000003@eagerm.com \
--to=eager@eagerm.com \
--cc=gdb@sourceware.org \
--cc=jan.kratochvil@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