Hi,
I've actually just been running openssl in ddd 2 days ago.
Here' the basic configuration I use: ./Configure --openssldir=<where I want openssl> 386 linux-elf
To compile openssl with the support for debugging
./Configure --openssldir=path/to/openssl/with/debugging 386 linux-elf:"gcc -g"
build, test, then install: make make tests make install
Then, if what you want to debug is actually an application that uses OpenSSL, you have to make sure that you link that application against the version of OpenSSL that you just compiled, i.e
gcc -g <myapp.c> -o myapp path/to/openssl/with/debugging/lib/libcrypto.a
Hope this helps.
Best, Jacques Thomas
Frosty Frosty wrote:
Hi
If I remember correctly, youo have to compile the OpenSSL source with the debug flag activated (check your compiler's manual; e.g. with gcc you have to add the option -g). Once you have the binaries, you can open them with DDD and follow the execution. Normally you don't have to use the "Open Source" menu entry, as DDD opens the source files as the execution flow moves from one to another
Frosty Frosty
Gurpreet Grewal wrote:
I need to trace through OpenSSL code to see the flow of things when I use it for some processing. I am trying to use DDD for the same but haven't been able to do so. When I try to do "Open Source" from the "File" menu, it doesnt show me any files which I can open and set up my break points.
Any ideas would be helpful..
Thanks Gurpreet ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
