From: Aurelian Melinte <ame01@gmx.net>
To: psmith@gnu.org, gdb@sourceware.org
Subject: Re: GDB 10.1: Backtrace goes into infinite loop
Date: Sat, 21 Nov 2020 15:33:58 -0500 [thread overview]
Message-ID: <29c86d7f-4b7c-c393-bd72-04c22028477a@gmx.net> (raw)
In-Reply-To: <3b63c3503a31dabc42315cb133e434c158759a46.camel@gnu.org>
On 21/11/2020 13:48, Paul Smith via Gdb wrote:
> On Sun, 2020-11-15 at 20:04 -0500, Simon Marchi wrote:
>> 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.
> Hi Simon; thanks for the reply. Just to say that this is still
> happening and I've now heard from two people on my team who see this
> behavior.
>
> I have not seen it though. I'm asking them to provide me with
> reproduction core files and binaries. As soon as I have this I will
> investigate further.
>
> Cheers!
I remember having seen this with a C++ clang compiled binary. At the
time I thought it loops over static data members in classes. E.g. you
have a class C, a static of it s and a member in C which would return a
ref/ptr to s.
HTH
--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
next prev parent reply other threads:[~2020-11-21 20:34 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
2020-11-21 18:48 ` Paul Smith
2020-11-21 20:33 ` Aurelian Melinte [this message]
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=29c86d7f-4b7c-c393-bd72-04c22028477a@gmx.net \
--to=ame01@gmx.net \
--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).