breakpoint on empty lines = NO OP
Bug #681091 reported by
The Escapist
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| gnusim8085 |
New
|
Undecided
|
Unassigned | ||
Bug Description
a breakpoint that is added to a line that does not contain an instruction is handled like a "NO OP" at the moment, this applies for example to empty lines or lines containing comments:
jmp start
start:
; empty line here (set breakpoint)
mvi a,255
hlt
Most people would probably expect that the breakpoint applies to the next valid instruction instead, so that they can literally be added "in between" instructions, without requiring the breakpoint to be in the same line as the instruction itself.
At the moment, such breakpoints are not handled at all
Revision history for this message
| The Escapist (wisd00m) wrote | #1 |
To post a comment you must log in.
It's worth noting that this also applies to breakpoints that are set on data/variable lines:
; ----------------
jmp start
foo: db 0,32,11,21,22 ; set breakpoint here
start: hlt
; -------------
Such breakpoints are obviously "NO OPS" in the current implementation.
it would probably be more correct to either disallow setting execution breakpoints here, or to specify a "data access" breakpoint according to https:/