On Tue, Nov 9, 2010 at 6:16 PM, <[email protected]> wrote:
>
>> > > + tst_resm(TINFO, "child %d verifies memory content.",
>> proc);
>> > > + for (j = start; j < end; j++)
>> > > + for (i = start2; i < end2; i++)
>> > > + if (memory[proc][j][i] != value)
>> > > + tst_resm(TFAIL,
>> > > + "child %d has %c at
>> > %d,%d,%d.",
>> > > + proc, memory[proc][j][i],
>> > proc,
>> > > + j, i);
>> >
>> > memcmp'ing a fixed buffer should be considerably faster verifying
>> > values byte by byte.
>> OK. Thanks.
> After further looking for this, it turned out memcmp did not offer the
> flexibility that when the verification failed like which byte caused the
> failure and its actual value to help with debugging.
Well... ok. How about doing the memcmp, and if things fail narrow
it down from there? Comparing things byte-by-byte is a long and
lengthy task :/...
Thanks!
-Garrett
------------------------------------------------------------------------------
The Next 800 Companies to Lead America's Growth: New Video Whitepaper
David G. Thomson, author of the best-selling book "Blueprint to a
Billion" shares his insights and actions to help propel your
business during the next growth cycle. Listen Now!
http://p.sf.net/sfu/SAP-dev2dev
_______________________________________________
Ltp-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ltp-list
