GDB internal error with "-stack-info-depth" command

[Sid Price]

When debugging an Apollo3 (Cortex-M) application that uses FreeRTOS, if a breakpoint is set in one of the tasks GDB crashes. The reported error is:

~"Breakpoint 1, usfsmax_read (reg=<optimized out>, size=<optimized out>, pBuf=<optimized out>) at ./src/usfsmax_task.c:296\n"
~"296\t usfsmax_get_status();\n"
*stopped,reason="breakpoint-hit",disp="keep",bkptno="1",frame={addr="0x0000c662",func="usfsmax_read",args=[{name="reg",value="<optimized out>"},{name="size",value="<optimized out>"},{name="pBuf",value="<optimized out>"}],file="./src/usfsmax_task.c",fullname="F:\\DataRoot\\Projects\\Equla\\USFSMAX_Test\\src\\usfsmax_task.c",line="296",arch="armv7e-m"},thread-id="1",stopped-threads="all"
(gdb)
-stack-info-depth --thread 1 10
~"/mnt/workspace/workspace/GCC-9-pipeline/jenkins-GCC-9-pipeline-200_20200521_1590053374/src/gdb/gdb/inline-frame.c:156: internal-error: void inline_frame_this_id(frame_info*, void**, frame_id*): Assertion `frame_id_p (*this_id)' failed.\nA problem internal to GDB has been detected,\nfurther debugging may prove unreliable.\nQuit this debugging session? (y or n)

This is a show-stopper for debugging the system, especially since the debugging client needs to evaluate the stack in order to present data.