Devin Acker
1ba3486fdb
get rid of redundant address field in symbol struct
2022-11-19 15:37:33 -05:00
qwertymodo
4a2c19f87e
Add toggle to log breakpoints without actually breaking ( #280 )
2021-12-16 00:09:22 -05:00
devinacker
b255a87fbc
make sure exec breakpoints are only highlighted in the correct debug view
2019-09-07 15:15:38 -04:00
devinacker
8bb6e4d80c
add popup completer for symbol names in breakpoint editor
2019-07-05 19:17:49 -04:00
devinacker
935ff10916
show a symbol name for breakpoint addresses if possible
2019-07-04 23:42:48 -04:00
devinacker
789d616974
add configurable comparison operators for breakpoints (see #133 )
2019-07-01 22:56:11 -04:00
devinacker
41e260cd6e
revamp breakpoint editor, allow adding/deleting an unlimited number of breakpoints
2019-06-30 03:14:40 -04:00
Benjamin Schulte
20aee2187f
allow to set breakpoints from disassembler
2018-11-24 20:44:20 -05:00
Benjamin Schulte
5ca2da30ce
allow to break on startup and on BRK
2018-11-24 20:38:16 -05:00
devinacker
e4c125b1c8
allow saving/reloading breakpoints between sessions
2017-04-24 23:53:53 -04:00
Marcus Rowe
bc6f2c3ead
Create breakpoints using the command line arguments
...
This allows me to use a script to automatically fill the bsnes debugger
with breakpoints. For instance, the following bash line:
bsnes --show-debugger `grep BREAKPOINT "$symfile" | awk '{print "-b " $1 ":x"}'` "$romfile"
Will open the debugger window and create a CPUBus execute breakpoint
for all symbols containing BREAKPOINT in the symbol file.
See `bsnes --help` or `Application::printArguments` for the format of
the breakpoint string.
2016-10-27 05:47:56 +10:00
devinacker
25375ff064
allow using WDM opcode as a software breakpoint
2015-11-16 20:31:54 -05:00
devinacker
9583a262c8
get rid of cumbersome "enable breakpoint" checkbox
2015-08-11 22:41:08 -04:00
devinacker
c42f1f430b
add ranged breakpoints and combinable r/w/x flags
2015-04-09 23:58:54 -04:00
devinacker
d88ac78d30
initial commit
2014-11-26 18:35:12 -05:00
