Re: deadlock in filesystem?

Peter Dimov wrote:

Is it possible that your program is using the multithreaded runtime but the filesystem library has been compiled as single threaded, or vice versa?

Certainly with Borland win32 builds, all libraries (bar thread obviously) default to single threaded. I've had to build all libraries as the multi-threaded version. Dead-lock was the result I saw because of waiting on the spin-lock in a shared_ptr (app was multi-threaded, signals library was single threaded in my case) Cheers Russell