On Sat, Jun 04, 2016 at 02:23:53PM +0100, Steve McIntyre wrote:
[...]
>  * The strace -S test fails when building/running using a 32-bit
>    userspace and a 64-bit kernel - the output includes both 64-bit and
>    32-bit tracing which confuses the test. I have a hacky fix.

Thanks Steve.  Since strace-S.test IS expected to test different
personalities properly, the proper fix is to trace a locally built
executable instead.

I also changed the test to measure wall clock time instead of system time
because of some subtle (Debian specific?) bug with -c option resulting to
first 3 columns of -c output containing zeroes only.  While that bug needs
a fix, it has nothing to do with -S option.


-- 
ldv

Attachment: pgp1ceO5JgCND.pgp
Description: PGP signature

------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity 
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Strace-devel mailing list
Strace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/strace-devel

Reply via email to