The main drawback with DEBUG is that in a code disassembly, the branch
and link's do not show the target procedure name. With a little
analysis, a good disassembler could show those targets. Or am I missing
something?

John Zoltak
North American Mfg Co

> -----Original Message-----
> From: Gavin Scott [SMTP:[log in to unmask]]
> Sent: Wednesday, July 01, 1998 2:47 PM
> To:   [log in to unmask]
> Subject:      [HP3000-L] Decomp for PA-RISC
>
> John asks,
> > Does anyone know of a decompiler/disassembler like the old DECOMP
> for
> > the classic system, but for PA-RISC systems.
> > I check the CSL but there are only the ones for the classic systems.
>
> Depends on what you want to do.  If you just want to explore a program
> then DEBUG will let you do just about anything you would want.  Just
> :RUN program;DEBUG and off you go.  A couple useful debug commands
> which you can execute in this order to get started:
>
> won        - turn windows on.
> pl 10      - Change "length" of the "p" window to $10 lines.
> grk        - kill the general register window to make more room for
> the
>              code display.  Useful if only displaying code, not
> debugging.
> pl 15      - Change p window to $15 lines after making room with grk.
> pj main    - jump the p window to the start of the main function.
> woff       - turn windows off.
> procl $$m@ - List code symbols beginning with the name $$m.
> help       - debug has lots of help.
> abort      - terminate the program ans quit debug.
>
> Avatar (available from Lund as part of the LPS Toolbox) is another
> option as has been mentioned, but I'll defer to Stan for why it's
> better than DEBUG, since I've never really used it.
>
> G.