[RTEMS Project] #4739: Fatal errors running GDB testcase against libdebugger

RTEMS trac trac at rtems.org
Mon Oct 10 14:12:51 UTC 2022

#4739: Fatal errors running GDB testcase against libdebugger
 Reporter:  Kévin Le Gouguec  |       Owner:  Chris Johns
     Type:  defect            |      Status:  new
 Priority:  normal            |   Milestone:
Component:  lib/debugger      |     Version:  6
 Severity:  normal            |  Resolution:
 Keywords:                    |  Blocked By:
 Blocking:                    |

Comment (by Kévin Le Gouguec):

 >  The person who did the aarch64 libdebugger port is on holiday so I
 thought I would ask a couple of questions while they were away.

 Thanks for following up in the meantime!

 >  Is the commit you mentioned from a git bisect or just the random hash
 >  were testing against?

 It happened to be the tip of the master branch when I started working on a
 reproducer; we originally observed this on 6c36cb7a486 "aarch64: always
 boot into EL1NS" (2022-01-12).

 >  Did you happen to test this with RTEMS build with SMP disabled?

 Not yet; I'll note to give it a try.

 >  And were you testing against real hardware or qemu? I don't recall
 which architectures qemu supports enough to even let libdebugger work.
 Since it has its own gdb server, often it does not simulate the needed
 debug registers/capabilities.

 We are testing against QEMU (7.0.0 plus some patches).  FWIW, in the
 context of our debugger testsuite, we are finding libdebugger more
 reliable than `qemu -gdb`.  The former has its share of issues, but at
 least results are mostly reproducible from one run to the next; QEMU's
 built-in GDB server on the other hand is much less deterministic in our

Ticket URL: <http://devel.rtems.org/ticket/4739#comment:2>
RTEMS Project <http://www.rtems.org/>
RTEMS Project

More information about the bugs mailing list