This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug gdb/20021] New: cannot run batch mode with close stdin
- From: "moorel at ntlworld dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Fri, 29 Apr 2016 11:11:27 +0000
- Subject: [Bug gdb/20021] New: cannot run batch mode with close stdin
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=20021
Bug ID: 20021
Summary: cannot run batch mode with close stdin
Product: gdb
Version: 7.11
Status: NEW
Severity: critical
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: moorel at ntlworld dot com
Target Milestone: ---
Hi
I have recently upgraded from gdb 7.9 to gdb 7.11, and the behavior for running
batch mode has changed.
In our system we are using gdb to run on the target simulator using a batch
command script, so usage is of the form
$ gdb --batch --command gdb.cmd
When this is run in a shell with a terminal all is well, but when run remotely
without a terminal it fails, effectively this can be reproduced locally by
doing the following to close the standard input
$ gdb --batch --command gdb.cmd < /dev/null | tee gdb.log
or
$ gdb --batch --command gdb.cmd 0<&- | tee gdb.log
any ideas why this is now failing, whereas it worked in version 7,9 ?
The failure I get is that it drops out from runing the bath commands early
Thx
Lee
--
You are receiving this mail because:
You are on the CC list for the bug.