This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug gdb/15791] New: Without TTY, the order of output in stdout and stderr is undetermined
- From: "qiyao at gcc dot gnu.org" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Fri, 26 Jul 2013 13:22:08 +0000
- Subject: [Bug gdb/15791] New: Without TTY, the order of output in stdout and stderr is undetermined
- Auto-submitted: auto-generated
http://sourceware.org/bugzilla/show_bug.cgi?id=15791
Bug ID: 15791
Summary: Without TTY, the order of output in stdout and stderr
is undetermined
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: qiyao at gcc dot gnu.org
When I ssh to localhost as below, there is no TTY.
$ ssh 127.0.0.1 /home/yao/Source/gnu/gdb/build-git/x86/gdb/gdb
GNU gdb (GDB) 7.6.50.20130724-cvs
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word".
(gdb) set width 0
(gdb) set height 0
(gdb) delete breakpoint 0
warning: bad breakpoint number at or near '0'(gdb)
delete breakpoint 0
warning: bad breakpoint number at or near '0'
(gdb) quit
As we can see, the order of warning and gdb prompt varies from run to run. I
can reproduce the problem when I ssh to cygwin and start a mingw32 native GDB.
This problem causes some fails in remote host testing.
--
You are receiving this mail because:
You are on the CC list for the bug.