public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "sergiodj at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug python/17372] python hangs when displaying help()
Date: Sat, 13 Sep 2014 00:05:00 -0000 [thread overview]
Message-ID: <bug-17372-4717-KbIL5NMh15@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17372-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=17372
Sergio Durigan Junior <sergiodj at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |palves at redhat dot com,
| |sergiodj at redhat dot com
--- Comment #1 from Sergio Durigan Junior <sergiodj at redhat dot com> ---
I can confirm this bug, and after bisecting GDB I found that the commit which
introduced the failure is:
commit 0017922d0292d8c374584f6100874580659c9973
Author: Pedro Alves <palves@redhat.com>
Date: Mon Jul 14 19:55:32 2014 +0100
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2014-09-13 0:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-11 9:02 [Bug python/17372] New: " serge.chatroux at st dot com
2014-09-11 9:03 ` [Bug python/17372] " serge.chatroux at st dot com
2014-09-13 0:05 ` sergiodj at redhat dot com [this message]
2014-10-23 11:58 ` palves at redhat dot com
2014-10-24 12:06 ` palves at redhat dot com
2014-10-29 17:33 ` cvs-commit at gcc dot gnu.org
2014-10-29 18:15 ` cvs-commit at gcc dot gnu.org
2014-10-29 18:33 ` palves at redhat dot com
2014-10-29 19:48 ` cvs-commit at gcc dot gnu.org
2014-12-25 0:46 ` cvs-commit at gcc dot gnu.org
2015-01-14 12:38 ` cvs-commit at gcc dot gnu.org
2015-01-14 12:43 ` cvs-commit at gcc dot gnu.org
2015-01-14 13:18 ` cvs-commit at gcc dot gnu.org
2021-10-21 6:51 ` bap.fayol at gmail dot com
2021-11-09 8:33 ` johnsjvi95 at gmail dot com
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-17372-4717-KbIL5NMh15@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).