gnusim8085-devel team mailing list archive

[The Escapist <681091@xxxxxxxxxxxxxxxxxx>]

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://bugs.launchpad.net/gnusim8085/+bug/579347

-- 
breakpoint on empty lines = NO OP
https://bugs.launchpad.net/bugs/681091
You received this bug notification because you are a member of
GNUSim8085 developers, which is subscribed to gnusim8085.

Status in gnusim8085: New

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