On Wed, Feb 09, 2011 at 04:10:13AM +0300, Dmitry V. Levin wrote:
> On Thu, Feb 03, 2011 at 12:10:01AM +0300, Dmitry V. Levin wrote:
> > On Wed, Feb 02, 2011 at 02:38:29PM -0500, Lavrentiev, Anton (NIH/NLM/NCBI) 
> > [C] wrote:
> > > 
> > > Could you please confirm the limitation noted in $subject?
> > 
> > Yes, this is a known issue I hope to fix.
> 
> I've just pushed a fix to the git HEAD, you can find it at
> http://strace.git.sourceforge.net/git/gitweb.cgi?p=strace/strace;a=commitdiff;h=v4.5.20-64-g65c1a81

Just a few words explaining the fix.

I had to replace switch(known_scno(tcp)) with a bunch of
sysent[tcp->scno].sys_func checks because __NR_read == 0 on x86-64 and
known_scno() consequently treats sysent[tcp->scno].native_scno
initialized with __NR_read as uninitialized.

This __NR_read case seems to be the only collision because on other
architectures syscall number 0 is usually assigned to__NR_restart_syscall.
Therefore, other uses of known_scno() should be safe.


-- 
ldv

Attachment: pgpFBmny2ItqS.pgp
Description: PGP signature

------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Strace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/strace-devel

Reply via email to