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 tapsets/12748] New: need syscall-number database in tapset


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

           Summary: need syscall-number database in tapset
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: tapsets
        AssignedTo: systemtap@sourceware.org
        ReportedBy: fche@redhat.com


For use by process().syscall and kernel.trace("sys_{enter,exit}"),
scripts need to know the syscall numbering conventions for the
current process.  A tapset should give it to them, perhaps in
the form:

global __syscall_32_num2name[400]
global __syscall_32_name2num[400]
global __syscall_64_num2name[400]
global __syscall_64_name2num[400]

probe begin { 
  .... initialize based on %( arch ... %)
}

function syscall_num(name) {
  return (current_is32bit() ? __syscall_32[name] : __syscall_64[name])
}
function syscall_name(num) { 
  ....
}

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.


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