Announcement

Collapse
No announcement yet.

Debugger Errors

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Debugger Errors

    Where can I find the meaning of specific debugger errors.

    Especially error 136 and error 196


    ------------------
    Thanks,

    Doug Gamble
    mailto:[email protected][email protected]</A>
    Thanks,

    Doug Gamble
    [email protected]

  • #2
    There are no "undocumented" error codes, so if you do encounter an undocumented error number, you can be pretty sure it is an indication of a memory corruption problem in your program.

    Typical causes of memory corruption include pointer errors, calling convention or parameter passing errors, bad inline-assembler code, etc. Outside of the debugger (and with no #DEBUG ERROR ON metastatement present) the most common cause is accessing arrays outside of their bounds. The debugger uses an implicit #DEBUG ERROR ON, so when an array element reference is outside of thr bounds of the array, you'll find that the ERR system variable will be set to 9, the statement causing th error will be ignored, and the code will otherwise continue running.

    I hope this helps!



    ------------------
    Lance
    PowerBASIC Support
    mailto:[email protected][email protected]</A>
    Lance
    mailto:[email protected]

    Comment

    Working...
    X