public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: V Bruce Hunt <vbhunt@gmail.com>
To: overseers@sourceware.org
Subject: GDB asked me to report the following:
Date: Thu, 20 Jan 2022 11:37:11 -0800	[thread overview]
Message-ID: <CACTRiLwsAEpcRHgvTjZ1grxB0gX-5vAWXAm5b2KyPiF1G+-Esw@mail.gmail.com> (raw)

I did a brief search of the bugbase and used the fields "gccbuild:gdb-10.1"
and "component;infrun.c:5690"  along with "internal error".  I got no
intelligible response. Reporting the bug requires a user account, but
creation is restricted.

Below is a copy of the interaction leading to the bug.  I'm happy to share
the full program source leading to the bug.  The bug appears on a 4GB
Raspberry Pi 4 running the latest version of the full version of Raspberry
Pi OS.  I'm using it with OpenOCD to debug a Raspberry Pi Pico through a
Picoprobe. The software is an under-development port of KU Trace by Richard
Sites that uses the Raspberry Pi Pico SDK and the SMP port for the
Pico/Rp2040 of FreeRTOS running on the RP2040 MPU ( A dual core ARM Cortex
V6 processor).

I will report this bug and others that may occur as I work to commission
KUtrace for the RP2040 with FreeRTOS if you think it appropriate by
allowing me to create a gdb bugzilla account.  I have run development teams
at Apple( Apple Consulting Engineering, Apple Integrated Systems) and Adobe
( Director of Engineering, Adobe Photoshop Album, Manager of Internet
Technology for Adobe's Advanced Technology Group.)

-----------gdb transcript leading to the "internal
error"----------------------------

Please check TERMINAL tab (gdb-server) for output from
/home/vbhunt/pico/openocd/src/openocd
Launching server: "/home/vbhunt/pico/openocd/src/openocd" "-c" "gdb_port
50000" "-c" "tcl_port 50001" "-c" "telnet_port 50002" "-s"
"/home/vbhunt/pico/openocd/tcl" "-f" "interface/picoprobe.cfg" "-f"
"target/rp2040.cfg"
Launching GDB: "/bin/gdb-multiarch" "-q" "--interpreter=mi2"
 "/home/vbhunt/projects/kutrace/build/main.elf"Set "showDevDebugOutput":
true in your "launch.json" to see verbose GDB transactions here. Helpful to
debug issues or report problems
Reading symbols from /home/vbhunt/projects/kutrace/build/main.elf...
warning: multi-threaded target stopped without sending a thread-id, using
first non-exited thread
isr_hardfault () at
/home/vbhunt/pico/pico-sdk/src/rp2_common/pico_standard_link/crt0.S:98
98 decl_isr_bkpt isr_hardfault
Program stopped, probably due to a reset and/or halt issued by debugger
target halted due to debug-request, current mode: Thread
xPSR: 0xf1000000 pc: 0x000000ee msp: 0x20041f00
target halted due to debug-request, current mode: Thread
xPSR: 0xf1000000 pc: 0x000000ee msp: 0x20041f00
target halted due to debug-request, current mode: Thread
xPSR: 0xf1000000 pc: 0x000000ee msp: 0x20041f00
target halted due to debug-request, current mode: Thread
xPSR: 0xf1000000 pc: 0x000000ee msp: 0x20041f00
Note: automatically using hardware breakpoints for read-only addresses.
target halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x00000178 msp: 0x20041f00

Thread 1 hit Temporary breakpoint 3, main () at
/home/vbhunt/projects/kutrace/main.c:197
197 {
target halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x10000fcc psp: 0x20025740

Thread 1 hit Breakpoint 1, prvKUtraceTask (pvParameters=0x20010438
<KUaffinityCore+4>) at /home/vbhunt/projects/kutrace/ku_initial.c:511
511 {
target halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x10000fcc psp: 0x20025740

Thread 1 hit Breakpoint 2, prvKUtestTask (pvParameters=0x200001c8
<KUtestTaskParms>) at /home/vbhunt/projects/kutrace/ku_initial.c:646
646 {
target halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x10000fcc psp: 0x20025740
target halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x10000fcc psp: 0x20025740
[Switching to Thread 2]

Thread 2 hit Breakpoint 1, prvKUtraceTask (pvParameters=0x20010434
<KUaffinityCore>) at /home/vbhunt/projects/kutrace/ku_initial.c:511
511 {
/build/gdb-vC73A7/gdb-10.1/gdb/infrun.c:5690: internal-error: int
finish_step_over(execution_control_state*): Assertion
`ecs->event_thread->control.trap_expected' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.

Quit this debugging session?
(y or n) [answered Y; input not from terminal]






*This is a bug, please report it.  For instructions,
see:<https://www.gnu.org/software/gdb/bugs/
<https://www.gnu.org/software/gdb/bugs/>>./build/gdb-vC73A7/gdb-10.1/gdb/infrun.c:5690:
internal-error: int finish_step_over(execution_control_state*): Assertion
`ecs->event_thread->control.trap_expected' failed.A problem internal to GDB
has been detected,further debugging may prove unreliable.*

Create a core file of GDB?
(y or n) [answered Y; input not from terminal]

-----------------End of Transcript
-------------------------------------------
Regards
V Bruce Hunt
mailto: vbhunt@silverfox.com, vbhunt@gmail.com

                 reply	other threads:[~2022-01-20 19:37 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CACTRiLwsAEpcRHgvTjZ1grxB0gX-5vAWXAm5b2KyPiF1G+-Esw@mail.gmail.com \
    --to=vbhunt@gmail.com \
    --cc=overseers@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).