We are producing a DLL in Visual Studio. That DLL when called by a VB application crashes the application in production. It does not crash it in debug mode. We produce a very similar DLL and successfully call it in a different VB application with no issues whatsoever. What should we be looking at for a cause?
I know, I know...don't use Visual Studio. But, I'm just trying to logically figure this thing out. It makes no sense.
Oh...let me add that the exact same code compiled in Pelles does not crash the app.
Either the DLL has a bug, or the VB app which uses it has a bug. There's nothing particularly mysterious about a bug that happens in release but not debug build.
Code://try //{ if (a) do { f( b); } while(1); else do { f(!b); } while(1); //}
What about the Pelles compiled code not crashing the app? Any idea as to why that version works?
It probably doesn't work, it just probably fails in a slightly less violent manner, say by corrupting already allocated memory rather than trying to write to unallocated memory (which triggers the crash).
Attach the Visual Studio debugger, interact with the VB app in a manner which causes the crash, profit. Now you know what causes it, rather than just 'It crashes'. Consider investing some of your time in learning how to figure out these basics, it'll help you spin your wheels in a more efficient manner.
