The specific CFLAG addition in the make file that works is /Zi which means to
generate full debug information.
derick
Yesterday I ran into the same problem. After some trial
and error, I was able to get it to work by editing nt.mak and changing
the CFLAG variable to:
CFLAG= /MT /Od -DDEBUG -D_
but needless to
say
> that's not really ideal.
>
> Bob
>
> -Original Message-
> From: owner-openssl-us...@openssl.org
>
> [mailto:owner-openssl-us...@openssl.org] On Behalf Of Carter Browne
> Sent: Friday, April 17, 2009 2:08 PM
> To: openssl-us...@openssl
wner-openssl-us...@openssl.org] On Behalf Of Carter Browne
Sent: Friday, April 17, 2009 2:08 PM
To: openssl-users@openssl.org
Subject: Re: Debugging OpenSSL with Visual Studio 2008
If you use the step into option when you start debugging, then the debugger
will step through the program starting from th
1:38 PM
> To: openssl-users@openssl.org
> Subject: Re: Debugging OpenSSL with Visual Studio 2008
>
> It is hard to reply without knowing what you are trying to do, but if you
> put a break point at the :"arg.data=NULL;" statement and then use the step
> over, step into op
re loaded.
Bob
-Original Message-
From: owner-openssl-us...@openssl.org
[mailto:owner-openssl-us...@openssl.org] On Behalf Of Carter Browne
Sent: Friday, April 17, 2009 1:38 PM
To: openssl-users@openssl.org
Subject: Re: Debugging OpenSSL with Visual Studio 2008
It is hard to reply without k
It is hard to reply without knowing what you are trying to do, but if
you put a break point at the :"arg.data=NULL;" statement and then use
the step over, step into options of the debugger, you should be able to
get to the area you are looking for. If VC tells you the breakpoint
won't be reached,
