Re: System call number cached with help from SyscallObserver

[Yao Qi <qiyaoltc at cn dot ibm dot com>]

On Wed, Sep 20, 2006 at 02:02:40PM -0600, Tom Tromey wrote:
> >>>>> "Yao" == Yao Qi <qiyaoltc@cn.ibm.com> writes:
> 
> If that isn't always the case, or if the cost of this lookup is too
> high, then another plan would be to have two kinds of SyscallEventInfo
> objects -- one used on entry and one on exit.  This seems a bit tricky
> since getReturnCode relies on getting the syscall number, at the moment.
> 
> What do you think of this?
I prefer the latter one.

I still have two questions in my mind,

1) Shall we create two objects of SyscallEventInfo, or extend two new
classes from SyscallEventInfo?

2) Supposing there are two objects, one is about enter a syscall and
another is about exit a syscall.  Does object about enter syscall
cache the system call number? (I think yes)  If object about enter a
syscall cache the syscall number, how could it pass this system call
number to the object about exit a system call?

-- 
Yao Qi