| Bug ID | 1103239 |
|---|---|
| Summary | valgrind doesn't understand -z separate-code linked objects |
| Classification | openSUSE |
| Product | openSUSE Tumbleweed |
| Version | Current |
| Hardware | x86-64 |
| OS | Other |
| Status | NEW |
| Severity | Normal |
| Priority | P5 - None |
| Component | Development |
| Assignee | bnc-team-screening@forge.provo.novell.com |
| Reporter | rguenther@suse.com |
| QA Contact | qa-bugs@suse.de |
| Found By | --- |
| Blocker | --- |
When linking with -z separate-code (which is the default on x86_64 starting
with binutils 2.31 currently in staging) valgrind doesn't seem to find
debuginfo
anymore.
Reproduce like
> echo 'int main() { return 0; }' | gcc -g -Wl,-z,separate-code -x c -
> valgrind --tool=callgrind ./a.out
> grep main callgrind.out.*
fn=(220) (below main)
fn=(14) dl_main
while the correct one looks like
cfn=(220) (below main)
fn=(246) main
fn=(14) dl_main