Read about our upcoming Code of Conduct on this issue

Commit e6d60b36 authored by alex@thinkpad's avatar alex@thinkpad
Browse files

GDB scripts: updated CURRENT_ISR for 100D and 1300D to use the latest hypothesis

(right before the interrupt ID, there is a counter telling whether we are running from interrupt or not, on all models so far)

--HG--
branch : qemu
parent 675e0e0aa2aa
......@@ -9,7 +9,7 @@ source -v debug-logging.gdb
#symbol-file ../magic-lantern/platform/100D.101/stubs.o
macro define CURRENT_TASK 0x652AC
macro define CURRENT_ISR (MEM(0x652B0) ? MEM(0x64C) >> 2 : 0)
macro define CURRENT_ISR (MEM(0x648) ? MEM(0x64C) >> 2 : 0)
# GDB hook is very slow; -d debugmsg is much faster
# ./run_canon_fw.sh will use this address, don't delete it
......
......@@ -9,7 +9,7 @@ source -v debug-logging.gdb
#symbol-file ../magic-lantern/platform/1300D.110/stubs.o
macro define CURRENT_TASK 0x31170
macro define CURRENT_ISR (MEM(0x31174) ? MEM(0x640) >> 2 : 0)
macro define CURRENT_ISR (MEM(0x63C) ? MEM(0x640) >> 2 : 0)
# GDB hook is very slow; -d debugmsg is much faster
# ./run_canon_fw.sh will use this address, don't delete it
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment