On Wed, May 1, 2013 at 10:27 PM, Angel Java Lopez <ajlopez2000@...>wrote:
John, usually I don't find the case "this test corrupts that test", and I
wrote thousands of tests.
Actually... it happened on every one.
As soon as you touch the heap, you have changed the system state.
If it's a GC'd language this isn't quite so problematic, but you still get
other resource leaks.
Have you free'd them all?
Well, you can run your tests under something like valgrind and it will tell
you.
Now which test leaked?
--
------------------------------
This email, including any attachments, is only for the intended recipient.
It is subject to copyright, is confidential and may be the subject of legal
or other privilege, none of which is waived or lost by reason of this
transmission.
If you are not an intended recipient, you may not use, disseminate,
distribute or reproduce such email, any attachments, or any part thereof.
If you have received a message in error, please notify the sender
immediately and erase all copies of the message and any attachments.
Unfortunately, we cannot warrant that the email has not been altered or
corrupted during transmission nor can we guarantee that any email or any
attachments are free from computer viruses or other conditions which may
damage or interfere with recipient data, hardware or software. The
recipient relies upon its own procedures and assumes all risk of use and of
opening any attachments.
------------------------------
