public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "qiyao at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug python/16470] Crash when inspecting STL containers with GDB pretty print Date: Sun, 26 Jan 2014 09:28:00 -0000 [thread overview] Message-ID: <bug-16470-4717-KQiYVBagEB@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-16470-4717@http.sourceware.org/bugzilla/> [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain; charset="UTF-8", Size: 4192 bytes --] https://sourceware.org/bugzilla/show_bug.cgi?id=16470 Yao Qi <qiyao at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |qiyao at gcc dot gnu.org --- Comment #1 from Yao Qi <qiyao at gcc dot gnu.org> --- (In reply to Axel Müller from comment #0) > > I installed the python pretty printers for STL from the GNU website and load > them in my .gdbinit. Where can we get the python pretty printer? and how do you load them into GDB? > GDB crashes when I inspect the STL list. > > To reproduce from the command line: > gdb -i mi -nx > > -enable-pretty-printing > -gdb-set print object on > source /home/amueller/.gdbinit We don't know what your ~/.gdbinit is, so could you please give us the steps in your ~/.gdbinit? -- You are receiving this mail because: You are on the CC list for the bug. >From gdb-prs-return-15118-listarch-gdb-prs=sources.redhat.com@sourceware.org Sun Jan 26 18:24:34 2014 Return-Path: <gdb-prs-return-15118-listarch-gdb-prs=sources.redhat.com@sourceware.org> Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 16410 invoked by alias); 26 Jan 2014 18:24:34 -0000 Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: <gdb-prs.sourceware.org> List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org> List-Archive: <http://sourceware.org/ml/gdb-prs/> List-Post: <mailto:gdb-prs@sourceware.org> List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs> Sender: gdb-prs-owner@sourceware.org Delivered-To: mailing list gdb-prs@sourceware.org Received: (qmail 16374 invoked by uid 48); 26 Jan 2014 18:24:33 -0000 From: "jan.kratochvil at redhat dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/16505] New: internal SIGFPE busy-CPU locks up GDB Date: Sun, 26 Jan 2014 18:24:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jan.kratochvil at redhat dot com X-Bugzilla-Status: NEW X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cf_gcchost attachments.created Message-ID: <bug-16505-4717@http.sourceware.org/bugzilla/> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2014-q1/txt/msg00126.txt.bz2 Content-length: 1239 https://sourceware.org/bugzilla/show_bug.cgi?id\x16505 Bug ID: 16505 Summary: internal SIGFPE busy-CPU locks up GDB Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: jan.kratochvil at redhat dot com Host: x86_64-unknown-linux-gnu Created attachment 7372 --> https://sourceware.org/bugzilla/attachment.cgi?ids72&actioníit trivial 1/0 reproducer When SIGFPE happens in GDB (for example due to corrupted DWARF file): Actual: PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 22602 jkratoch 20 0 243188 90680 39960 R 97.3 1.5 0:12.50 gdb + GDB under GDB: Program received signal SIGFPE, Arithmetic exception. 0x00000000007d076e in process_die (die=0x2531c40, cu=0x23d1b80) at dwarf2read.c:8031 8031 volatile int i=a/b; (gdb) _ Expected: ../../gdb/dwarf2read.c:8031: internal-error: A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n) _ -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2014-01-26 9:28 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 [this message] 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 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-KQiYVBagEB@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).