diff options
Diffstat (limited to 'results/classifier/zero-shot/108/debug/2279')
| -rw-r--r-- | results/classifier/zero-shot/108/debug/2279 | 40 |
1 files changed, 40 insertions, 0 deletions
diff --git a/results/classifier/zero-shot/108/debug/2279 b/results/classifier/zero-shot/108/debug/2279 new file mode 100644 index 000000000..496549738 --- /dev/null +++ b/results/classifier/zero-shot/108/debug/2279 @@ -0,0 +1,40 @@ +debug: 0.954 +graphic: 0.951 +other: 0.923 +device: 0.832 +performance: 0.828 +semantic: 0.784 +network: 0.762 +vnc: 0.707 +files: 0.690 +socket: 0.685 +permissions: 0.626 +PID: 0.616 +KVM: 0.506 +boot: 0.462 + +Debugging with Lauterbach Trace32 -> Cortex-A76, no SP register update +Description of problem: +We do not see changes in the SP_EL1 register value when debugging the QEMU application with Lauterbach Trace32. +Steps to reproduce: +1. Compile bare metal code that uses push and pop instructions (stack). +2. Run QEMU with bare metal code. +3. Connect via Lauterbach Trace32 and check the displayed SP register value. +Additional information: + +This is a screenshot from QEMU 8.0.0, but updating to QEMU 8.2.0 does not resolve the problem. + +I have discussed this with Lauterbach Trace32 support with these results: +- Trace32 uses RSP protocol `p` packets to read some registers, including SP_EL1. GDB seems to use `g` packet. +- QEMU responds to `p` packet with an invalid value, which causes Trace32 to display invalid value. + +Some related RSP protocol logs from Trace32. + + + +Different part of RSP protocol log: +``` +Sending packet: $p20#d2 ... +receiving packet: ec00004000000000 +``` +So it looks like Trace32 can receive different values that zero as response to `p` packet. |