Hi,
'trinity' generated an io_submit call with a ludicrous large
'nr' of requests, the result being strace sat there just printing out
{...}, for nearly ever since the data didn't exist.
Is the right thing to 'break' rather than 'continue' if either
of the umove calls fail? The alternative way is to break
if the iocbs read fails but allow individualy broken iocb reads.
I'm not sure which is more sane - you could have a real call
that fails for another reason before hitting the bad iocb.
Dave
--
-----Open up your eyes, open up your mind, open up your code -------
/ Dr. David Alan Gilbert | Running GNU/Linux | Happy \
\ gro.gilbert @ treblig.org | | In Hex /
\ _________________________|_____ http://www.treblig.org |_______/
------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________
Strace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/strace-devel
