public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "beaux_monde at tut dot by" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug python/16470] Crash when inspecting STL containers with GDB pretty print Date: Wed, 15 Sep 2021 07:02:06 +0000 [thread overview] Message-ID: <bug-16470-4717-2WID7Wd9sW@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-16470-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=16470 Serge Roussak <beaux_monde at tut dot by> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |beaux_monde at tut dot by --- Comment #5 from Serge Roussak <beaux_monde at tut dot by> --- This bug is reproduced on my machine too. I use the Eclipse CDT IDE and this bug may break the debugging because the gdb is crashed sometimes with exactly the same symptoms as described here and the same assertion is logged on the gdb trace console. I tried the different Eclipse CDT, gcc and gdb versions -- the bug is here. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-09-15 7:02 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-01-20 12:51 [Bug python/16470] New: " aegges at web dot de 2014-01-21 8:41 ` [Bug python/16470] " marc.khouzam at ericsson dot com 2014-01-26 8:12 ` xhpohanka at gmail dot com 2014-01-26 9:28 ` qiyao at gcc dot gnu.org 2014-01-27 7:21 ` xhpohanka at gmail dot com 2014-01-27 8:31 ` qiyao at gcc dot gnu.org 2014-01-27 12:14 ` xhpohanka at gmail dot com 2021-09-15 7:02 ` beaux_monde at tut dot by [this message] 2022-06-07 15:36 ` tromey at sourceware dot org 2023-08-31 19:21 ` 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-16470-4717-2WID7Wd9sW@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).