[Info-vax] Debugging shareable images on Integrity

[jcwoman1963 at hotmail.com]

On Apr 23, 4:20 pm, koeh... at eisner.nospam.encompasserve.org (Bob
Koehler) wrote:
> In article <e7fd5699-f89a-45a6-bc81-a46506dd8... at c36g2000yqn.googlegroups.com>, jcwoman1... at hotmail.com writes:
>
>
>
> >   My image is installed with the INSTALL/SHARE command. No priv's or
> > other installer parameters.  The shareable modules and my application
> > are written in Macro.
>
>    Macro-32 or IA-64 macro?  If the latter, I would try stepping by
>    instruction as a workaround.
>
>    Is the main .entry also in Macro?  If not then try the set language
>    command.

It's I64-Macro.  Stepping by instruction displays the instruction, but
same behavior as before, STEP does nothing but display the same thing
over and over again.  I don't get the feeling that it's actually
executing the line/instruction, just displaying it.

Answer to JF:  Nope, I tried cancelling all the breaks and then
setting a new breakpoint at one of the lines beyond the .ENTRY and
then hitting GO.  It doesn't stop at the breakpoint.  STEP/INTO does
the same thing.

I wish I could post code for you guys, but this is a small but
integral piece of a very large system.  One of my coworkers commented
that he often pulls the code out of the shareable image and copies it
into his local application when he needs to debug, but it's alot of
work and he usually ends up quadrupling the size of his program just
to debug something.  I can do that, but would like to avoid it if at
all possible.  So nobody here has come across this odd behavior
before?