As a third-party library developer, I have to say this --Quote:
Originally Posted by ProgrammerC++
unless you can come up with a very simple example that demonstrates the error, then it will always be "your code" that is the cause of the crashes. You could be calling these functions out of sequence, on invalid handles, or you may have corrupted the heap in some way, etc.
The people that work on these libraries make all the effort to stamp out any bugs in their code. The only way to prove it really is the library is to have a code sample that does nothing except a few initializations, and calling the API functions that you're claiming cause random crashes.
I have seen too many times where the user claims "it's the library", and when the code the user wrote is finally analyzed, the code is full of bugs that can cause all sorts of havoc (i.e. passing uninitialized pointers to functions, improper handling of dynamically allocated memory, etc.)
Regards,
Paul McKenzie
