I have a very simple Delphi 2010 DLL that I load from the Visual Studio 2008 C ATL console application (MVF GUI app is not working either) When I debug the console app directly from the IDE - there is no breakpoint - Output from the app is not correct, but when I run the app directly or if I attach the process to the debugger So it works 100%. Debugging the same DLL (i.e. running with IDE) also works from the Delphi console app.
The VS debugger starts to break the app on the basis of it's running VS2010 does the same!
I've ensured 100% - many times! - That I can go into more detail in the data type and conventional congressional conference and consoles app match, but I do not want to confuse this issue with irrelevant information. Please tell me if I have to go into the characteristics of the code, if I have given the offer, it is not enough.
Has anyone experienced this kind and knows how to fix it?
I have found a problem once (in different behaviors and standalone applications in the IDE / debugger). It came to know that I have examined the value of the unset variable, Debugger had allocated it (always!) In the previously used block of memory, such that the price was not empty and the application worked correctly (because only Conditional block was incorrect). However, the OS sometimes adds an application to the empty memory block (filled with 0s), the condition is unsuccessful and the app has crashed.
Maybe this is a problem? Try using OutputDebugString () 'to track the values of variables during the library runtime, I believe without some source code, it is not easy to say, what might be the reason for this.
Best Relationship - Spook
Comments
Post a Comment