diff options
| author | Richard Levitte <levitte@openssl.org> | 2017-03-15 02:52:20 +0100 |
|---|---|---|
| committer | Richard Levitte <levitte@openssl.org> | 2017-03-15 03:09:57 +0100 |
| commit | 1ae4c07e50a4988c7e2263ad669dc75fe2d494cb (patch) | |
| tree | f8ce78bf369fe894c6f67796c19775b235e7d56c /NOTES.VMS | |
| parent | Add Python Cryptography.io external test suite (diff) | |
| download | openssl-1ae4c07e50a4988c7e2263ad669dc75fe2d494cb.tar.xz openssl-1ae4c07e50a4988c7e2263ad669dc75fe2d494cb.zip | |
VMS: don't use /DSF, turn off CALL_DEBUG instead
It turns out that /DSF didn't do any good for our purposes. Instead,
remove the CALL_DEBUG flag from any image we link. This ensures that
we can have debugging information in the image files, but don't
automatically end up in a debugging session upon image activation.
Unfortunately, this means the CALL_DEBUG must be turned on when there
is a need to run with the debugger activated, and to turn it off when
done. This has been documented in NOTES.VMS.
Reviewed-by: Rich Salz <rsalz@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/2957)
Diffstat (limited to 'NOTES.VMS')
| -rw-r--r-- | NOTES.VMS | 20 |
1 files changed, 20 insertions, 0 deletions
@@ -56,6 +56,26 @@ to use. + About debugging + --------------- + + If you build for debugging, the default on VMS is that image + activation starts the debugger automatically, giving you a debug + prompt. Unfortunately, this disrupts all other uses, such as running + test programs in the test framework. + + As a compromise, we're turning off the flag that makes the debugger + start automatically. If there is a program that you need to debug, + you need to turn that flag back on first, for example: + + $ set image /flag=call_debug [.test]evp_test.exe + + Then just run it and you will find yourself in a debuggin session. + When done, we recomment that you turn that flag back off: + + $ set image /flag=nocall_debug [.test]evp_test.exe + + Checking the distribution ------------------------- |