Unwanted Debug Window

hippy

Technical Support
Staff member
I can confirm that for no reason whatsoever, as previously reported by evilmonkh and pmolsen, a program that was compiling and downloading as expected, now brings up a Debug window when there are no debug commands present.

http://www.rev-ed.co.uk/picaxe/forum/Topic.asp?topic_id=1026
http://www.rev-ed.co.uk/picaxe/forum/Topic.asp?topic_id=1213

There seems to be no logic to what's causing the problem, but deleting some statements stop the debug window appearing, while others don't.

Programming Editor 4.1.4 - Listing sent to Rev-Ed.
 

Technical

Technical Support
Staff member
This is unavoidable at present. Due to internal operation of the debug command, the Programming Editor has to scan the compiled download file looking for the tokenised debug sequenece. On very rare occasions, particularly when using long strings or lookup tables, this sequence may be duplicated by byte data in a command rather than the debug command itself. In this case an unwanted debug window will appear.

We do not consider this a major issue as it happens very rarely and has no affect on the success of the download.
 

hippy

Technical Support
Staff member
This seems to be the result of poor object code parsing. It's entirely possible to accurately 'disassemble' the PICAXE 'object code' and identify which are command tokens and which are command arguments, and detect only actual DEBUG commands.
 

hippy

Technical Support
Staff member
Armed with the official explanation, I was able to get rid of the Debug window invokation by changing -

- LOOKDOWN b0,(22,26,85,89),b9

to

- LOOKDOWN b0,(85,89,22,26),b9
 
Top