This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
gdb/552: Test MI ``-target-select remote /dev/null''
- From: ac131313 at redhat dot com
- To: gdb-gnats at sources dot redhat dot com
- Date: 19 May 2002 20:13:13 -0000
- Subject: gdb/552: Test MI ``-target-select remote /dev/null''
- Reply-to: ac131313 at redhat dot com
>Number: 552
>Category: gdb
>Synopsis: Test MI ``-target-select remote /dev/null''
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: change-request
>Submitter-Id: net
>Arrival-Date: Sun May 19 13:18:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator: ac131313@redhat.com
>Release: 2002-05-19
>Organization:
>Environment:
>Description:
Need a testcase to check that the MI -target-select command reports an error when it fails. Compare:
(gdb)
-target-select remote /dev/null
&"get_tty_state failed: Operation not supported\n"
&"set_tty_state failed: Operation not supported\n"
&"get_tty_state failed: Operation not supported\n"
&"set_tty_state failed: Operation not supported\n"
~"Ignoring packet error, continuing...\n"
~"Ignoring packet error, continuing...\n"
~"Ignoring packet error, continuing...\n"
&"Couldn't establish connection to remote target\n"
&"Malformed response to offset query, timeout\n"
^connected
(gdb)
with:
(gdb)
-target-select remote /dev/null
&"get_tty_state failed: Operation not supported\n"
&"set_tty_state failed: Operation not supported\n"
&"get_tty_state failed: Operation not supported\n"
&"set_tty_state failed: Operation not supported\n"
~"Ignoring packet error, continuing...\n"
~"Ignoring packet error, continuing...\n"
~"Ignoring packet error, continuing...\n"
&"Couldn't establish connection to remote target\n"
&"Malformed response to offset query, timeout\n"
^error,msg="Malformed response to offset query, timeout"
(gdb)
Is the use of /dev/null legitimate?
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: