public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "simark at simark dot ca" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/27743] Internal error psymtab.c
Date: Mon, 19 Apr 2021 00:56:13 +0000	[thread overview]
Message-ID: <bug-27743-4717-Ef1Vo1iLs1@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27743-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=27743

--- Comment #7 from Simon Marchi <simark at simark dot ca> ---
(In reply to Ethan Zhang from comment #6)
> Currently it seems I can only reproduce it within "CLion" the IDE I'm using.

In CLion, there should be a way to get the "MI traces" or something like that,
the log of the communication between CLion and GDB.  I've never used CLion, so
I can't really help you there.  But if you can get that, it would be helpful to
reproduce the problem.  It will allow replaying the same steps, but without
CLion.

> 
> The internal failure happens when I compile the source file using
> arm-none-eabi-gcc 9 and debug it with GDB 10 connected to openOCD. Every
> time I attempt to set a break point using the IDE triggers the internal GDB
> failure.
> 
> With the exact same set up, directly setting a break point from a GDB
> terminal does not cause the failure. Even when debugging within the IDE,
> setting a break point from its own GDB terminal doesn't cause the internal
> failure.
> 
> I'm not sure where to go from here as I don't know what's different between
> me setting a break point from command line and the IDE setting a break point.

Since the bug happens while expanding a symtab, pPerhaps something that could
reproduce the problem:

1. Load your binary in GDB
2. Use the command "maintenance expand-symtabs".

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2021-04-19  0:56 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-16 12:57 [Bug gdb/27743] New: " ilia.motornyi at jetbrains dot com
2021-04-16 13:12 ` [Bug gdb/27743] " ilia.motornyi at jetbrains dot com
2021-04-16 14:09 ` simark at simark dot ca
2021-04-16 14:31 ` ilia.motornyi at jetbrains dot com
2021-04-17  3:04 ` cn.yiki at gmail dot com
2021-04-17 13:06 ` simark at simark dot ca
2021-04-17 15:46 ` tromey at sourceware dot org
2021-04-18  4:56 ` cn.yiki at gmail dot com
2021-04-19  0:56 ` simark at simark dot ca [this message]
2021-04-19  0:56 ` simark at simark dot ca
2021-04-19  1:51 ` tromey at sourceware dot org
2021-04-19  1:54 ` simark at simark dot ca
2021-04-19 11:55 ` cn.yiki at gmail dot com
2021-04-19 14:04 ` ilia.motornyi at jetbrains dot com
2021-04-19 14:23 ` cn.yiki at gmail dot com
2021-04-19 14:41 ` ilia.motornyi at jetbrains dot com
2021-04-19 14:45 ` simark at simark dot ca
2021-04-19 14:46 ` simark at simark dot ca
2021-04-23 12:03 ` ilia.motornyi at jetbrains dot com
2021-04-23 12:54 ` ilia.motornyi at jetbrains dot com
2021-04-23 15:27 ` tromey at sourceware dot org
2021-04-23 15:34 ` tromey at sourceware dot org
2021-04-23 18:14 ` tromey at sourceware dot org
2021-04-23 18:23 ` tromey at sourceware dot org
2021-04-23 18:49 ` brobecker at gnat dot com
2021-04-26 15:39 ` cvs-commit at gcc dot gnu.org
2021-04-26 15:40 ` cvs-commit at gcc dot gnu.org
2021-04-26 15:53 ` cvs-commit at gcc dot gnu.org
2021-04-26 15:55 ` 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-27743-4717-Ef1Vo1iLs1@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: 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).