This is the mail archive of the gdb-prs@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug remote/20643] New: Remote file IO not reset by run command


https://sourceware.org/bugzilla/show_bug.cgi?id=20643

            Bug ID: 20643
           Summary: Remote file IO not reset by run command
           Product: gdb
           Version: HEAD
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: remote
          Assignee: unassigned at sourceware dot org
          Reporter: jon at beniston dot com
  Target Milestone: ---

Created attachment 9532
  --> https://sourceware.org/bugzilla/attachment.cgi?id=9532&action=edit
Possible patch

Remote file I/O isn't reset after a run command. This means that if a program
is 'run' more than once, I/O from/to stdin/stdout may not work or the second
run, if the those descriptors were closed by the first run.

E.g:

tar ext-rem
run
"hello world"
run
* no output *

Looking at extended_remote_create_inferior(), it seems remote_fileio_reset() is
only called via extended_remote_restart(). It isn't called if the target
supports the run command.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]