🚀 go-pugleaf

From: ardvar!krs@stag.UUCP (Kent Schumacher)

I'm having a problem with a program I've written using Laser C
v2.0.  My program gets a four bomb (illegal instruction) error
when run.  Using Laser DB to check the problem shows that the
bomb comes from the first line of code which is an appl_init
call.  After some more digging, I realized that the JSR and data
references in the appl_init call were not being relocated (i.e.
the values for JSR and data addresses were the same as in the
listing of the symbol table - I cross checked this situation
using Allan Pratts DB).  More analysis resulted in the following
statistics:

Values are being relocated until an offset of 82,894 bytes into
the text segment.  This happens after 3583 relocations and 9
jumps (relocation bytes with a value of 1).  The next value to
be relocated happens at an offset of 82,914 bytes.  That value
and the following 689 values that should be relocated are not
getting relocated. gak.

My relocation data analyzer seems to indicate that the
relocation info is correct.  Since this behavior can be seen
using both Laser DB and Allans DB, and also seems to be present
when run from the desktop (four bombs), I have a hard time
blaming Laser C.  (Actually I'm having a hard time blaming
anything, which is why I'm bringing my problem to the net).

Does this behavior ring a bell with anyone?  Better yet, anybody
have a solution?

(Oh yeah, to save Allan from a flurry of requests for his
debugger, Allan Pratt's DB is available only to Atari ST
registered developers [I think]).  (And I suppose to save me
from a flurry of notes from Atari, I *am a registered
developer...)

  - Kent Schumacher                  /* "A member of STdNET-         */
    krs@ardvar.UUCP                  /*  The ST developers network  */