MV>> What does the 'pgm-ctr' stand for if you get a runtime error?
TH> I think that is the value of PC (stands for Program Counter, a
  > register that points the processor to the current
  > instruction/OP-code.
MV> I know...
 
Sorry. Just making sure... 
TH> PBC takes a command argument "/OM" that generates a .MAP file
  > that has xfed info, but they don't seem to correctly correspond
  > to the line actually making the error in the source code.
  > Further, the xref is in hex and the error is in decimal.
MV> The HEX-decimal-difference isn't the problem, I hope:-)
I converted it.
MV> On a really small program, the pgm-ctr seemed to make sense, the
  > pgm-ctr was higher than value of the line on which it occured,
  > but lower than the next line... But now, I get such a large value
  > that it can't even refer to an offset in the segment...
 
My values are usually greater than 60000.
 
TH> Of course, it does. It doesn't use PBD however, but some internal
  > process that I can not access.
MV> Maybe some secret command-line-option which is available on all
  > PB-programs:-) Like /ShowClearErrorMessages ...
 
The debugger is integrated into PB, it embeeds coding to work with
it.
TH> If I create a run time problem, and I can't figure it out, I will
  > go into PB and let it tell me what the error is. The debugger in
  > there seems to be okay, though I haven't had to lean on it that
  > much.
MV> You could do that, but of course, it WOULD be really neat if the
  > editor itself could give the line of the error, it would save you
  > lots of time..
I use QEdit, and I programmed the macros to point to the compile
errors. That works okay. However, I haven't been able to figure our
how to redirect the run-time errors. That's the bugger.
 
___ Blue Wave/QWK v2.12
--- Maximus/2 3.01
---------------