public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
* [Bug remote/8637] 'target remote' fails with named pipe
[not found] <bug-8637-4717@http.sourceware.org/bugzilla/>
@ 2013-07-01 13:20 ` tromey at redhat dot com
0 siblings, 0 replies; only message in thread
From: tromey at redhat dot com @ 2013-07-01 13:20 UTC (permalink / raw)
To: gdb-prs
http://sourceware.org/bugzilla/show_bug.cgi?id=8637
Tom Tromey <tromey at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tromey at redhat dot com
Summary|'target remote xxx' can |'target remote' fails with
|cause segmentation fault in |named pipe
|arm-elf-gdb |
--- Comment #2 from Tom Tromey <tromey at redhat dot com> ---
(In reply to nm127 from comment #0)
> Tring to use a named pipe (fifo) as target remote gives some error.
Now I get:
(gdb) target remote /tmp/QQQ
get_tty_state failed: Inappropriate ioctl for device
set_tty_state failed: Inappropriate ioctl for device
Remote debugging using /tmp/QQQ
get_tty_state failed: Inappropriate ioctl for device
set_tty_state failed: Inappropriate ioctl for device
Bogus trace status reply from target: qTStatus
gdb assumes that a file name given to "taret remote" is
a tty. It should probably check this with isatty before
applying ioctls to the fd; or use ser-pipe.c for named
pipes as well.
I'm changing the bug description as the SEGV problem
seems to be fixed.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2013-07-01 13:20 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <bug-8637-4717@http.sourceware.org/bugzilla/>
2013-07-01 13:20 ` [Bug remote/8637] 'target remote' fails with named pipe tromey at redhat dot com
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).