public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: psmith@gnu.org, gdb@sourceware.org
Subject: Re: GDB 10.1: Backtrace goes into infinite loop
Date: Sun, 15 Nov 2020 20:04:59 -0500	[thread overview]
Message-ID: <5553a2ee-6918-87e6-2283-3cbb37b9ec6f@simark.ca> (raw)
In-Reply-To: <503bd54a619aa2781d6b1385cbd3db20634addaa.camel@gnu.org>


On 2020-11-13 5:16 p.m., Paul Smith via Gdb wrote:
> Hi all;
>
> I just upgraded our users from a toolset using GCC 8.1.0, binutils
> 2.30, and GDB 8.2.1, to a new one using GCC 10.2, binutils 2.35.1, and
> GDB 10.1 (on GNU/Linux x86_64).
>
> Now some of my users are running into a problem where they run the "bt"
> command and it shows some subset of the stack frames, then jumps back
> and starts over printing from frame 0, and does this forever until you
> use ^C to stop it.
>
> Apparently this doesn't happen every time, and the number of frames
> that are shown are variable (but usually a smaller number like 2 to 5
> frames).  By "not every time" I mean after a breakpoint sometimes we
> get a good bt and sometimes it recurses, but if it recurses for a given
> bt it will always recurse (that is if you use ^C to stop then "bt"
> again it recurses again).
>
> If we do the same thing with the older GDB (keeping the newer
> compiler/binutils) then we don't see this behavior.
>
> FWIW, the code in question is C++ code and was compiled with -ggdb3 and
> no optimization.
>
> Just wondering if anyone has seen something like this, and/or how to
> try to collect more details.
>

Hi Paul,

When you see the problem happening, you could save a core file (just run
the generate-core-file command).  Then, try to reproduce the problem
using the core file.  If it reproduces, you could upload it to a bug
report.

Simon

  reply	other threads:[~2020-11-16  1:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-13 22:16 Paul Smith
2020-11-16  1:04 ` Simon Marchi [this message]
2020-11-21 18:48   ` Paul Smith
2020-11-21 20:33     ` Aurelian Melinte
2021-02-02  3:21 ` Repro case! " Paul Smith
2021-02-02  4:27   ` Paul Smith
2021-02-02 13:45     ` Paul Smith

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=5553a2ee-6918-87e6-2283-3cbb37b9ec6f@simark.ca \
    --to=simark@simark.ca \
    --cc=gdb@sourceware.org \
    --cc=psmith@gnu.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).