Drew,
I just took a quick glance at this trace--things look fine from the iRPC
end. I'd agree that the iRPC code ran and we attempted a call. I would
note that OneTimeCode's call target address is only 32-bits long on a
64-bit system. That could be coincidence, or perhaps some 'int'
truncation is happening somewhere.
Given the full DYNINST_DEBUG_PROCCONTROL trace, which will have library
load addresses, one could confirm that there is a library loaded over that
address.
Of course, if there wasn't anything there then I'd expect a SIGSEGV, and
that didn't happen.
-Matt
On Thu, 4 Apr 2013, Andrew Bernat wrote:
Yeah, we're making a call. Not sure to where; the address is 0xf6b42210. And you say you're not seeing your function get called?
Drew
On Apr 4, 2013, at 12:42 PM, David Smith <dsmith@xxxxxxxxxx> wrote:
f6b42210
--
Andrew Bernat
Paradyn Project
bernat@xxxxxxxxxxx
http://www.cs.wisc.edu/~bernat
|
![[Computer Systems Lab]](http://www.cs.wisc.edu/pics/csl_logo.gif){kind=logo}