This is the mail archive of the mailing list for the frysk 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]

Patch: add two accessors to Syscall

I was reading a thread on the valgrind list about finding where a bad
close() was called

and I thought this would be a simple thing for frysk to do.

First I wanted the appended patch to let my code inspect a Syscall.
Could someone check this in?  (I didn't add all the accessors, just
the ones I needed.)

I hacked up to do what I wanted (it was *very* easy this
way -- nice :-), but on my FC5 box I always get an I/O error when
trying to get the stack trace of a task (failure attached).  Any

Also I noticed a few other oddities here and there.  For instance,
SyscallEventInfo.returnCode returns a long -- but apparently does not
sign-extend the syscall's actual return value.  This leads to the
unobvious test:

    (int) syscallEventInfo.returnCode(task) < 0

I wasn't sure whether you'd prefer email about little things like this
or whether I should just drop stuff directly in bugzilla... let me


Attachment: P
Description: patch

Attachment: S
Description: stack trace

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