Debug a C DLL

[Jake Thompson]

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. Does anybody have any advice
on how to narrow down the problem. I put popups into the exe code to
narrow down the issue to the first dll call but I am at a loss as to
what would cause debug dll to work and the release version not to work.
I can generate a map but I am terrible at reading it and I function a
lot better when the error occurs in debug mode because then I can use
the debug tool. Would the map be the best approach or is there a
better method. If I generate a map could someone help me find the
correct location in the dll?

Thanks
Jake

[Mark McIntyre]

On 12 Jan 2006 15:13:21 -0800, in comp.lang.c , "Jake Thompson"
<re***********@hotmail.com> 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.

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 =----

[Karl Malbrain]

Mark McIntyre wrote:

On 12 Jan 2006 15:13:21 -0800, in comp.lang.c , "Jake Thompson"
<re***********@hotmail.com> 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

[Kenny McCormack]

In article <11**********************@f14g2000cwb.googlegroups .com>,
Jake Thompson <re***********@hotmail.com> 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.

Allow me to be the first to say this - and I say it from the deepness of my
heart, with all the kindness and love one has come to associate with the
helpful posts you get in this newsgroup:

Not portable. Can't discuss it here. Blah, blah, blah.

[Grumble]

Jake Thompson wrote:

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.

Try microsoft.public.win32.programmer.*

[Mark McIntyre]

On 12 Jan 2006 15:34:05 -0800, in comp.lang.c , "Karl Malbrain"
<ma******@yahoo.com> wrote:

Mark McIntyre wrote:

On 12 Jan 2006 15:13:21 -0800, in comp.lang.c , "Jake Thompson"
<re***********@hotmail.com> 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 =----