File: example-debugger

package info (click to toggle)
hatari 2.6.1%2Bdfsg-2
  • links: PTS
  • area: main
  • in suites: forky, sid
  • size: 11,236 kB
  • sloc: ansic: 167,249; cpp: 8,685; python: 6,324; objc: 1,888; asm: 1,754; sh: 1,688; javascript: 149; makefile: 87; xml: 32
file content (16 lines) | stat: -rw-r--r-- 696 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 GEMDOS is called with the Dgetdrv() opcode
# (happens e.g. when EmuTOS console prints the prompt):
breakpoint  GemdosOpcode = 0x19  :lock

# NOTE: in addition to information specified by "lock" command
# being printed, ":lock" flag causes breakpoint hit to just to
# be traced, instead of emulation dropping to debugger.
#
# 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.