From: "changbin.du at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug libdw/24856] New: dwarf_diename() cannot get correct name
Date: Sat, 27 Jul 2019 13:40:00 -0000 [thread overview]
Message-ID: <bug-24856-10460@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=24856
Bug ID: 24856
Summary: dwarf_diename() cannot get correct name
Product: elfutils
Version: unspecified
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: libdw
Assignee: unassigned at sourceware dot org
Reporter: changbin.du at gmail dot com
CC: elfutils-devel at sourceware dot org
Target Milestone: ---
Created attachment 11923
--> https://sourceware.org/bugzilla/attachment.cgi?id=11923&action=edit
object file
The allfcts get all symbols as the same name.
elfutils/tests$ ./allfcts ../../linux/kernel/iomem.o
kernel/iomem.c:162:x86_coreid_bits
kernel/iomem.c:139:x86_coreid_bits
kernel/iomem.c:134:x86_coreid_bits
kernel/iomem.c:129:x86_coreid_bits
kernel/iomem.c:122:x86_coreid_bits
kernel/iomem.c:71:x86_coreid_bits
kernel/iomem.c:30:x86_coreid_bits
kernel/iomem.c:16:x86_coreid_bits
./include/linux/mm.h:626:x86_coreid_bits
./include/linux/device.h:1105:x86_coreid_bits
./include/linux/mmzone.h:1297:x86_coreid_bits
./include/linux/mmzone.h:1262:x86_coreid_bits
./include/linux/mmzone.h:1212:x86_coreid_bits
./include/linux/mmzone.h:1151:x86_coreid_bits
./include/linux/page-flags.h:372:x86_coreid_bits
./include/linux/err.h:24:x86_coreid_bits
But dwfl API works:
elfutils/tests$ ./funcretval -e ../../linux/kernel/iomem.o
() devm_memunmap: returns no value
() devm_memremap: return value location: {0x50, 0}
() devm_memremap_match: return value location: {0x50, 0}
() devm_memremap_release: returns no value
() memunmap: returns no value
() memremap: return value location: {0x50, 0}
() try_ram_remap: return value location: {0x50, 0}
() arch_memremap_wb: return value location: {0x50, 0}
() is_vmalloc_addr: return value location: {0x50, 0}
() dev_to_node: return value location: {0x50, 0}
() pfn_valid: return value location: {0x50, 0}
() valid_section: return value location: {0x50, 0}
() __nr_to_section: return value location: {0x50, 0}
() pfn_to_section_nr: return value location: {0x50, 0}
() PageHighMem: return value location: {0x50, 0}
() ERR_PTR: return value location: {0x50, 0}
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2019-07-27 13:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-27 13:40 changbin.du at gmail dot com [this message]
2019-07-27 13:46 ` [Bug libdw/24856] " changbin.du at gmail dot com
2019-07-27 14:28 ` mark at klomp dot org
2019-07-27 14:29 ` mark at klomp dot org
2020-01-10 15:14 ` fche at redhat dot com
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=bug-24856-10460@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=elfutils-devel@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).