Re: How to debug Openssl DLL - Openssl

This is a discussion on Re: How to debug Openssl DLL - Openssl ; ------=_Part_9480_27539778.1205779237248
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Hi,
You can use the generated DLL's (I assume you've used the OpenSSL provided
batchfile/makefile set) with your project by adding them to the project
dependencies.
I do not know if this ...

Re: How to debug Openssl DLL

You can use the generated DLL's (I assume you've used the OpenSSL provided
batchfile/makefile set) with your project by adding them to the project
dependencies.

I do not know if this also suffices for VS2005 to 'see' the related source
code (you do not 'link' source code: it's rather that the VS2005 IDE must
have access to the source files from which the binary was generated - with
MSVC this is sometimes quite hard to achieve when you use makefiles or other
'non-MSVC-IDE' methods to generate object code from sources).

The other approach is to 'convert' the makefile to a (set of) MSVC2005
projects: then the OpenSSL source code will be considered by MSVC2005 as
just another project and it'll be easy to step through the SSL source code.
The cinch is 'converting to a MSVC2005 project': that's the hard part. ;-)

If you're interested, I plan to put a fresh set of MSVC2005 project files
on-line for OpenSSL somewhere next week; I use these to produce [private]
MSVC2005 debug (and production) releases.

You can use the generated DLL's (I assume you've used the OpenSSL provided batchfile/makefile set) with your project by adding them to the project dependencies.

I do not know if this also suffices for VS2005 to 'see' the related source code (you do not 'link' source code: it's rather that the VS2005 IDE must have access to the source files from which the binary was generated - with MSVC this is sometimes quite hard to achieve when you use makefiles or other 'non-MSVC-IDE' methods to generate object code from sources).

The other approach is to 'convert' the makefile to a (set of) MSVC2005 projects: then the OpenSSL source code will be considered by MSVC2005 as just another project and it'll be easy to step through the SSL source code. The cinch is 'converting to a MSVC2005 project': that's the hard part. ;-)

If you're interested, I plan to put a fresh set of MSVC2005 project files on-line for OpenSSL somewhere next week; I use these to produce [private] MSVC2005 debug (and production) releases.