[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | -={ H A C K E R S }=- |
| Notice: | Write locked - see NOTED::HACKERS |
| Moderator: | DIEHRD::MORRIS |
|
| Created: | Thu Feb 20 1986 |
| Last Modified: | Mon Aug 03 1992 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 680 |
| Total number of notes: | 5456 |
171.0. "Don't call us, we'll call you!" by RICARD::HEIN () Thu Oct 24 1985 13:45
Do you all know what the following instructions will achieve?
PUSHL #SS$_DEBUG
CALLS #1, G^LIB$SIGNAL
I found it 'by accident'. Very handy every so often! (not too often,
but still) It works on V4, and it did work on V3, but is it supposed
to work? Is it documented somewhere? Do YOU like it?
I used it first for some sort of transaction monitor, which mapped
in user images in its address space and had to be able to startup
the debugger when requested. Good fun that was! Unfortunatly I never
quite managed to hook up the debug symbol table for those mapped-in
images.
Have fun,
Hein van den Heuvel
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 171.1 | | PARVAX::PFAU | | Thu Oct 24 1985 18:58 | 4 |
| I believe this is supposed to work. I think that is what the DEBUG command
does to map the debugger into an already activated image.
tom_p
|
| 171.2 | | SPEEDY::BRETT | | Thu Oct 24 1985 22:50 | 6 |
| It has been a big hack to load the debugger this way for a long time.
I don't think this is documented, hence I don't think its guaranteed to
always work.
/Bevin
|
| 171.3 | | TOOLS::COWAN | | Thu Oct 31 1985 00:29 | 6 |
| The internals manual documents that SS$_DEBUG invokes the debugger.
Since SS$_DEBUG is in the same class hardware detected exceptions
(like SS$_ACCVIO), it may be documented in a more public place. Try
your friendly VAX Architecture standard.
KC
|
| 171.4 | | SPEEDY::BRETT | | Thu Oct 31 1985 08:00 | 5 |
| I think it would be more correct to say the internals manual documents that
V3 or V4 uses SS$_DEBUG to invoke the debugger. Unlike most of our
documentation the internals manuals document what is, not what will be.
/Bevin
|