This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug translator/2438] Can't resolve $fd argument for sys_readv and sys_writev on ppc64
- From: "fche at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sources dot redhat dot com
- Date: 9 May 2006 19:26:37 -0000
- Subject: [Bug translator/2438] Can't resolve $fd argument for sys_readv and sys_writev on ppc64
- References: <20060309040316.2438.hien@us.ibm.com>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- Additional Comments From fche at redhat dot com 2006-05-09 19:26 -------
(In reply to comment #5)
> [...] I just want
> to say the first instruction (X) after the prologue may probably modify
> the argument register, thus the location list entry will be inavailable.
It should not be unavailable. The compiler should spell out where the arguments
are for all instructions.
> Since our prehandler is executed before (X), thus we can use its preceding
> one (X-4) to ask for the location list entry.
That would only make sense if the location list information for address X was
built to represent the *after-image* of the instruction. I believe otherwise,
that the information represents the state *just before* the instruction would
be executed at address X. Therefore, using the location list for address X,
for a probe at address X, would be exactly correct.
If for some reason the data does not match this intent, then there is
probably a compiler bug.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=2438
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.