Please refresh the page to try again, or use Firefox. An error report has been sent to the developer
This tools finds strange behavior in Pep/8 programs by exploring all detectable execution paths.
Upon analyzing a program, this tool reports dead code blocks and data within the execution path. It also detects wrongful use of data such as accessing uninitialized memory, printing a word and reading code.
To use: copy-paste your code in the source code block and launch the analysis using the Analyze program button.
Shorthand are used in the error messages, some refer directly to the line numbers others to the address in the memory of the running program.
|web:5||Source line 5|
|L8||Source line 8|
|rA, rX||Registers A, X|
|m24||Memory at address 24 (bytes)|
|instr@m24||Intruction at address 24 (bytes). Usually, this would be the (24/4+1=) 7th instruction, if there is no data blocks. And the 7th line if there is no data blocks or comments.|
Note that the tool reports possible errors and strange behaviors. For an advanced or expert user, it may raise errors on correct code.
|... the CFG may be wrong||The program structure is too complex to analyze. This happens when jumping to dynamic addresses and when using switch statements.|
|unreachable instructions||There's dead code.|
|data in program flow||The program may execute raw data. There's probably a
|overwriting code at...||An instruction writes over an existing instruction (probably your code).|
|expected "type" in "address", got "something"||An instruction uses data with an unexepected type. It may be a