This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug uprobes/10458] New: uaddr() returns one past current instruction for uprobes


While writing a testcase for bug #10454 I noticed uaddr() returns one off
results for uprobes. That is, it returns the pc as if it is just after the
breakpoint (int3 trap) instruction.

a) do we consider this a bug?
b) where should this be fixed?
   alternatives are:
   - uprobes setting task_pt_regs REG_IP back just before the callback
   - uaddr just always substracting 1 (probably arch dependent)

-- 
           Summary: uaddr() returns one past current instruction for uprobes
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: uprobes
        AssignedTo: systemtap at sources dot redhat dot com
        ReportedBy: mjw at redhat dot com


http://sourceware.org/bugzilla/show_bug.cgi?id=10458

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]