public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "markus.mohrhard at googlemail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug python/16624] New: python pretty printers can turn into infinite loop when maximum recursion depth exceeded
Date: Fri, 21 Feb 2014 21:34:00 -0000 [thread overview]
Message-ID: <bug-16624-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=16624
Bug ID: 16624
Summary: python pretty printers can turn into infinite loop
when maximum recursion depth exceeded
Product: gdb
Version: 7.5
Status: NEW
Severity: normal
Priority: P2
Component: python
Assignee: unassigned at sourceware dot org
Reporter: markus.mohrhard at googlemail dot com
While debugging Libreoffice and trying to print mrModel in
TypeGroupConverter::createCategorySequence gdb starts to print out an infinite
number of Python Exceptions "maximum recursion deppth exceeded.
mrModel is of Type TypeGroupModel.
Attached is a backtrace of gdb while being in the loop. It seems I have already
5200 frames that all look similar.
I also checked our pretty printers and it seems that none is catching the
exception so I assume it must be in the gdb code itself.
System is OpenSuse 12.3 with gdb 7.5.1-2.1.1 and Libreoffice is a current
master --enable-dbgutil build.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2014-02-21 21:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-21 21:34 markus.mohrhard at googlemail dot com [this message]
2014-02-24 12:28 ` [Bug python/16624] " pmuldoon at redhat dot com
2014-02-24 12:52 ` markus.mohrhard at googlemail dot com
2023-08-31 16: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-16624-4717@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).