public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "marc.khouzam at ericsson dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug breakpoints/15182] New: Pagination is triggered for dprintf Date: Sat, 23 Feb 2013 13:59:00 -0000 [thread overview] Message-ID: <bug-15182-4717@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=15182 Bug #: 15182 Summary: Pagination is triggered for dprintf Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: breakpoints AssignedTo: unassigned@sourceware.org ReportedBy: marc.khouzam@ericsson.com Classification: Unclassified Pagination is triggered for dprintf in CLI mode. I have seen this when using dprintf-style 'gdb' but I didn't try the "call" mode because it does not work on my Ubuntu machine. I think pagination is a problem for dprintf because: a) when pagination is triggered, inferior execution will be interrupted until the user answers the pagination prompt b) pagination is triggered by the dprintf but not by real inferior output. So, as dprintf and inferior printouts appear interleaved on the screen, the pagination prompt will be triggered when the dprintfs add up to too many, which will seem random to the user, since the other printouts are also visible. -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next reply other threads:[~2013-02-23 13:59 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-02-23 13:59 marc.khouzam at ericsson dot com [this message] 2013-04-18 8:58 ` [Bug breakpoints/15182] " teawater at gmail dot com 2013-04-18 8:59 ` teawater at gmail dot com 2013-04-26 7:57 ` teawater at gmail dot com 2013-05-03 10:38 ` marc.khouzam at ericsson dot com 2013-05-03 10:45 ` marc.khouzam at ericsson dot com 2013-06-27 18:47 ` marc.khouzam at ericsson 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-15182-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: 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).