We develop a network library that uses TCP and UDP sockets.
This DLL is used by a testclient, which is started multiple times at the same PC for a load test.
In Windows Vista, it is no problem to start the testclient many times.
In Windows XP, starting it up to 5 times is no problem, but if we start it 6 times or more, and then closing one client, ALL of them crash with apparently random stack traces.
Yes, although we do not use any interprocess code (only sockets between the clients), the termination of one of the client leads to the crash of all of them.
Our DLL is compiled with MSVC and uses Boost and Crypto++ libs (statically linked).
Any idea why the different processes could influence each other?
An idea: You have some bug.
Seriously, there is no way to know what’s your problem without any information what so ever.
When a process crashes it usually has a very good reason to do so. find out what that is.
Compile your dlls and executables in debug, attach a debugger and make sense of the stack trace you get. if you get a nonsense stack trace, find out why that is.
As with many problems, this one is likely to be solved by “Just debugging it”