You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My use case for tarmac-browser often involves checking the context in which a CPU exception occurred. To do this, I search for CoreEvent in the tarmac file, to get a timestamp to jump to in tarmac-browser. It would be more convenient if tarmac-browser had a way to jump directly to the next/previous CPU exception.
CPU exceptions are represented as events in the tarmac file, but tarmac-browser treats them as TextOnlyEvents. Here is an example of the tarmac for an exception, this was from a Cortex-A9 FastModel:
9036000000 ps IT (9036) 10015f70 e4913004 A svc_s : LDR r3,[r1],#4
9036000000 ps MR4 1001fbe2 (ABORTED)
9036000000 ps E 10015f70 abt 00000019 CoreEvent_ModeChange
9036000000 ps E 10015f70 00000005 CoreEvent_handleDataAbort
9036000000 ps R r14_abt 10015f78
9036000000 ps R cpsr 200001d7
9036000000 ps R spsr_abt 200001d3
9036000000 ps R DFSR_S 00000001
9036000000 ps R DFAR_S 1001fbe2
9036000000 ps R SPSR_abt 200001d3
9036000000 ps SIGNAL: SIGNAL=DebugReset STATE=N
9036000000 ps SIGNAL: SIGNAL=ResetHold STATE=N
The text was updated successfully, but these errors were encountered:
My use case for
tarmac-browser
often involves checking the context in which a CPU exception occurred. To do this, I search forCoreEvent
in the tarmac file, to get a timestamp to jump to intarmac-browser
. It would be more convenient iftarmac-browser
had a way to jump directly to the next/previous CPU exception.CPU exceptions are represented as events in the tarmac file, but
tarmac-browser
treats them asTextOnlyEvent
s. Here is an example of the tarmac for an exception, this was from a Cortex-A9 FastModel:The text was updated successfully, but these errors were encountered: