public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "joachim.protze at zih dot tu-dresden.de" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug tui/14332] New: Output from inferior confuses gdbtui Date: Thu, 05 Jul 2012 13:10:00 -0000 [thread overview] Message-ID: <bug-14332-4717@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=14332 Bug #: 14332 Summary: Output from inferior confuses gdbtui Product: gdb Version: 7.4 Status: NEW Severity: normal Priority: P2 Component: tui AssignedTo: unassigned@sourceware.org ReportedBy: joachim.protze@zih.tu-dresden.de Classification: Unclassified Created attachment 6510 --> http://sourceware.org/bugzilla/attachment.cgi?id=6510 print 20 lines of "hello world!" To reproduce: gcc -g hello2.c -o hello gdb -ex run -tui ./hello The first "Hello World!\n" is overwritten by the gdb output, therefore the printf is in a for-loop. Two symptoms can be viewed: - the \n produces a line feed only, no carriage return - the output of the inferior is not fetched and reported in the output subscreen -- 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:[~2012-07-05 13:10 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-07-05 13:10 joachim.protze at zih dot tu-dresden.de [this message] 2015-07-02 13:04 ` [Bug tui/14332] " palves at redhat dot com 2015-07-02 13:05 ` palves at redhat dot com 2023-01-23 0:32 ` levraiphilippeblain at gmail dot com 2023-05-22 16:24 ` vries at gcc dot gnu.org 2023-05-24 14:13 ` vries at gcc dot gnu.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-14332-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).