This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: Question regarding userspace tracing memcpy in glibc
- From: Roland McGrath <roland at redhat dot com>
- To: fche at redhat dot com (Frank Ch. Eigler)
- Cc: Holger Hans Peter Freyther <holger at freyther dot de>, "Ariel Shaqed (Scolnicov)" <ariels at correlix dot com>, systemtap at sources dot redhat dot com
- Date: Tue, 4 Jan 2011 10:19:06 -0800 (PST)
- Subject: Re: Question regarding userspace tracing memcpy in glibc
- References: <loom.20101126T174831-857@post.gmane.org> <y0mfwung32s.fsf@fche.csb> <AANLkTi=u3vUTnMU+4C0-0mS2t5hzDjz1Q+DLZ-Ku+c7d@mail.gmail.com> <y0mbp4tldqd.fsf@fche.csb> <4D131DFA.7010009@freyther.de> <y0moc7w1r2v.fsf@fche.csb>
> That's one possibility. Another is running "as -g --gdwarf-2", which
> I believe glibc does not use that in its build of .s files.
It does. But that only generates source location information, not a full
DIE tree with function names and types and so forth (which the assembler
doesn't know anyhow). The notion has come up before to get more complete
information in there, either via glibc hacks or via new assembler features.
But there is a bunch of work involved (more of it being deciding how to go
about it and how to compose the interface for assembler features than
anything else).
Thanks,
Roland