http://bugzilla.novell.com/show_bug.cgi?id=1000513
http://bugzilla.novell.com/show_bug.cgi?id=1000513#c3
Michael Matz changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |matz@suse.com
--- Comment #3 from Michael Matz ---
Actually why would there be debug info for e.g. 'getenv' in coreutils-debuginfo
at all? It comes from glibc and _there_ it should have full debug info,
not just prototypes.
(Normally GCC doesn't emit debug info for functions that are merely declared.
Even if they are used. E.g.:
#include
#include
int main() { printf("%s\n", getenv("PATH")); return 0; }
doesn't generate debug info for either getenv or printf. So what needs to be
checked as well is if coreutils-debuginfo does or doesn't contain debug info
for e.g. getenv. If it does, then why. And if it doesn't then why is ltrace
confused by it non-presence?
Jiri: can you look at coreutils-debuginfo if it contains getenv entries?
(Use readelf -wi for inspection).
--
You are receiving this mail because:
You are on the CC list for the bug.