Re: Debug a C DLL

On 12 Jan 2006 15:34:05 -0800, in comp.lang.c , "Karl Malbrain"
<malbrain@xxxxxxxxx> wrote:

>
>Mark McIntyre wrote:
>> On 12 Jan 2006 15:13:21 -0800, in comp.lang.c , "Jake Thompson"
>> <readytoride39@xxxxxxxxxxx> wrote:
>>
>> >Hello,
>> >
>> >I have an exe that calls a dll. The dll is dynamically loaded and I
>> >use getprocaddress to get the address of the funciton I want to call.
>> >
>> >Everything seems to work fine in debug mode but in release mode it is
>> >blowing up at the first call to the dll.
>>
>> You should ask this question again in a Windows programming group,
>> where the experts at this sort of stuff hang out. My guess is that
>> you're corrupting memory by overruning an array, or using unitialised
>> variables or something, and in debug mode you get away with it because
>> your debug build is more tolerant.
>
>Actually, you have this backward. The debug build has more error
>checking. karl m

No, I have it forward. The debug build typically has more tolerance of
faults, eg it initialises auto variables to zero, puts in overflow
space round arrays and structs, etc etc.


Mark McIntyre
--

----== Posted via Newsfeeds.Com - Unlimited-Unrestricted-Secure Usenet News==----
http://www.newsfeeds.com The #1 Newsgroup Service in the World! 120,000+ Newsgroups
----= East and West-Coast Server Farms - Total Privacy via Encryption =----
.

Relevant Pages

  • Re: [VS2008 SP1][std::vector] _CRT_DEBUGGER_HOOK crash in Release mode only
    ... _SECURE_SCL and _HAS_ITERATOR_DEBUGGING are both enabled by default in debug mode. ... Note that if you enable _HAS_ITERATOR_DEBUGGING, make sure to enable it for *every* projects in your solution (in fact, H.I.D. changes the structure and logic of STL classes, so it is not correct to mix STL classes that have H.I.D. enabled with STL classes with the same name but with H.I.D. disabled.) ... For Release mode, you might want to check that all of your projects use Multi-threaded DLL, in case you are going to pass C++ classes through DLL boundaries. ...
    (microsoft.public.vc.language)
  • RE: 800a01ad error while debugging VB6 DLL under IIS6.0 on Win2003SP1
    ... I am looking for possible solutions to debug it using terminal server. ... A VB6.0 DLL works fine when called from ASP page without debug mode. ...
    (microsoft.public.win32.programmer.ole)
  • RE: 800a01ad error while debugging VB6 DLL under IIS6.0 on Win2003SP1
    ... I am looking for possible solutions to debug it using terminal server. ... A VB6.0 DLL works fine when called from ASP page without debug mode. ...
    (microsoft.public.vb.com)
  • RE: There is no source code available for the current location.
    ... I've verified all of the items that Robert wrote about and found them to be correct. ... This is a C# application, using a Managed C++ DLL, which sometimes calls a C# DLL. ... Verify that you are in debug mode and not release mode. ...
    (microsoft.public.vsnet.debugging)
  • Re: How to connect to children process
    ... Main problem is amount of manual operations required per debug cycle. ... connection to DLL with debugger takes sensible amount of time and manual ... Is the main problem that the debugger keeps symbols file loaded ... AFAIK that's how VS2003 debugger works, but WinDbg should usually ...
    (microsoft.public.vsnet.debugging)
Loading