From: Tom Tromey <tromey@redhat.com>
To: 朱庆 <zqing1986@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: [help] Linux kernel debug error: Cannot find DIE
Date: Wed, 11 Jul 2012 20:40:00 -0000 [thread overview]
Message-ID: <87mx36doam.fsf@fleche.redhat.com> (raw)
In-Reply-To: <CAEO5vgtGHPzoqC=ZsYumDMnDU6to3BcenNWNcyeKMky=ASnhiQ@mail.gmail.com> (=?utf-8?B?IuacseW6hiIncw==?= message of "Wed, 11 Jul 2012 17:32:05 +0800")
>>>>> ">" == 朱庆 <zqing1986@gmail.com> writes:
>> Dwarf Error: Cannot find DIE at 0x1634a7 referenced from DIE at
>> 0x17a459 [in module linux-kernel/linux-2.6.32.6/Build/vmlinux]
>> I'm not sure this is caused by incorrect dwarf info generated by
>> open64 compiler or gdb issues, since the gcc build kernel binary is
>> able to debug.
>> I compared the dwarf info output of the two compiler with objdump
>> --dwarf=info , open64's binary is about 1.95GB and gcc's binary is
>> 1.72GB, is that too large?
>> Can someone give any clue on this to determine what is wrong here?
There isn't an easy way to know what has gone wrong here.
It could be incorrect DWARF -- meaning a compiler or (less likely)
linker bug. Or, it could be a gdb bug.
I would debug it by using objdump or readelf to look at the DWARF around
the DIEs mentioned in the error message.
The size of the DWARF is probably not an issue.
At least, this is not the error I would expect in that situation.
Tom
next prev parent reply other threads:[~2012-07-11 20:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-11 9:32 朱庆
2012-07-11 20:40 ` Tom Tromey [this message]
2012-07-12 8:44 ` 朱庆
2012-07-24 19:19 ` Tom Tromey
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=87mx36doam.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb@sourceware.org \
--cc=zqing1986@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).