remove non-determinism from client.events test

From derek.br...@gmail.com on April 13, 2009 10:40:30

the client.events test has some non-determinism that leads to failures in its various runs and clutters up our test results:

deletion event coming at different times
app (events.c) fprintf(stderr not serialized with client (events.dll.c) dr_printf (xref Issue 110 )

ideas:

sort output before comparing: but would like to verify that callback 2 was called BEFORE callback 1
instead of printing set a flag and at end check the flags and print which ones are missing