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/17586] New: Clarity needed on use of "remote:" in path names


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

            Bug ID: 17586
           Summary: Clarity needed on use of "remote:" in path names
           Product: gdb
           Version: 7.8
            Status: NEW
          Severity: normal
          Priority: P2
         Component: remote
          Assignee: unassigned at sourceware dot org
          Reporter: dje at google dot com

On a whim I tried the following.

bash1$ gdbserver --multi :1234
bash2$ gdb
(gdb) tar ext :1234
(gdb) symbol-file remote:hello.x64
(gdb) exec-file remote:hello.x64
remote:hello.x64: No such file or directory.
(gdb) exec-file ~/src/play/hello.x64
(gdb) set remote exec-file ./hello.x64
(gdb) start

and got

`remote:hello.x64' has disappeared; keeping its symbols,
but otherwise things appear to work (I didn't try too much though).

Given that gdb did fetch hello.x64 from gdbserver (set debug remote 1), I
wouldn't expect the "has disappeared" error.

Also, if symbol-file accepts "remote:" I don't see why exec-file can't.

I can imagine symbol-file accepts "remote:" only accidentally.
If so, we should make it flag an error until we're ready to properly support
it.

-- 
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]