File: example-debugger

package info (click to toggle)
hatari 2.0.0%2Bdfsg-3
  • links: PTS
  • area: main
  • in suites: stretch
  • size: 12,112 kB
  • ctags: 16,421
  • sloc: ansic: 146,916; python: 5,460; objc: 1,856; sh: 945; asm: 757; makefile: 152; xml: 32
file content (16 lines) | stat: -rw-r--r-- 710 bytes parent folder | download | duplicates (4) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
 
# Show disassembly from address in A0 when debugger is entered:
lock regaddr disasm a0

# Track when GEMODS is called with the Dgetdrv() opcode
# (happens e.g. when EmuTOS console prints the prompt):
breakpoint  GemdosOpcode < 0xffff  &&  GemdosOpcode = 0x19  :lock

# NOTE: "info" flag above will cause this to be just traced and
# information specified by "lock" command above to be printed,
# debugger won't interrupt the emulation.
#
# This is important when using hconsole because entering the Hatari
# debugger (and its line editing) will mess up the terminal from
# which hconsole is run from.  At least until user has blindly
# typed "cont" to the Hatari debugger so that Hatari emulation
# continues.