public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "johnsjvi95 at gmail dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug python/17372] python hangs when displaying help() Date: Tue, 09 Nov 2021 08:33:10 +0000 [thread overview] Message-ID: <bug-17372-4717-NbnfVDTZao@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-17372-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=17372 Stewart <johnsjvi95 at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |johnsjvi95 at gmail dot com --- Comment #13 from Stewart <johnsjvi95 at gmail dot com> --- The first part of python help is displayed and a 'help>' prompt is displayed. But I can no more enter commands to display the end of the help. I need to suspend/restore gdb using CTRL-Z and fg to be able to enter new commands. https://springfieldpaintingpros.com -- You are receiving this mail because: You are on the CC list for the bug.
prev parent reply other threads:[~2021-11-09 8:33 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 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 [this message]
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-NbnfVDTZao@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).