public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "jerome.pouiller at gmail dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug remote/27927] gdb crash with OpenOCD Date: Tue, 01 Jun 2021 08:14:27 +0000 [thread overview] Message-ID: <bug-27927-4717-ixKXGLNJcy@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-27927-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=27927 --- Comment #4 from Jérôme Pouiller <jerome.pouiller at gmail dot com> --- I still have the problem with the commit-id a2cf3633 (01/06/2021). I have compiled gdb with: ./configure --prefix=/tmp/gdb --disable-shared --enable-static --target=arm-none-eabi Beside the line number, the error message is the same: $ /tmp/gdb/bin/arm-none-eabi-gdb /tmp/foo3/build/debug/foo.out GNU gdb (GDB) 11.0.50.20210601-git Copyright (C) 2021 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "--host=x86_64-pc-linux-gnu --target=arm-none-eabi". Type "show configuration" for configuration details. For bug reporting instructions, please see: <https://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... /home/jerome/.gdbinit:37: Error in sourced command file: ~/conf/_gdbinit-gef.py:57: Error in sourced command file: Undefined command: "from". Try "help". Reading symbols from /tmp/foo3/build/debug/foo.out... (gdb) target extended-remote localhost:3333 Remote debugging using localhost:3333 thread.c:1345: internal-error: void switch_to_thread(thread_info*): Assertion `thr != NULL' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. This is a bug, please report it. For instructions, see: <https://www.gnu.org/software/gdb/bugs/>. [1] 621480 abort (core dumped) /tmp/gdb/bin/arm-none-eabi-gdb /tmp/foo3/build/debug/foo.out $ -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-06-01 8:14 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-28 12:47 [Bug remote/27927] New: " jerome.pouiller at gmail dot com 2021-05-28 12:49 ` [Bug remote/27927] " jerome.pouiller at gmail dot com 2021-05-28 12:52 ` jerome.pouiller at gmail dot com 2021-05-28 13:40 ` simark at simark dot ca 2021-06-01 8:14 ` jerome.pouiller at gmail dot com [this message] 2021-06-01 8:21 ` jerome.pouiller at gmail dot com 2021-06-01 8:23 ` jerome.pouiller at gmail dot com 2021-06-01 13:43 ` simark at simark dot ca 2021-06-01 13:44 ` simark at simark dot ca 2021-06-02 6:22 ` alucca388 at gmail dot com 2021-06-02 7:06 ` jerome.pouiller at gmail dot com 2021-06-02 7:26 ` jerome.pouiller at gmail dot com 2021-06-02 7:29 ` jerome.pouiller at gmail dot com 2021-06-02 13:28 ` simark at simark dot ca 2021-11-06 9:04 ` fredrik.hederstierna@securitas-direct.com 2022-06-29 13:43 ` robertjenssen at ozemail dot com.au 2023-01-17 16:28 ` tromey at sourceware dot org 2023-02-09 14:40 ` jerome.pouiller at gmail dot com 2023-02-09 14:43 ` jerome.pouiller at gmail dot com 2023-02-09 21:45 ` tromey at sourceware dot org
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=bug-27927-4717-ixKXGLNJcy@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@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: linkBe 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).