Print the "file" command suggestion in exec_file_locate_attach
authorJan Kratochvil <jan.kratochvil@redhat.com>
Wed, 6 Apr 2016 13:57:08 +0000 (15:57 +0200)
committerJan Kratochvil <jan.kratochvil@redhat.com>
Wed, 6 Apr 2016 13:57:08 +0000 (15:57 +0200)
commitfef3cb9f3aa84018d10866f89228ae3f23e5ca7e
tree91ff8134277961ab695c5fa892bc441cb08f52e5
parent15dd01b1209ec92b361dd2547708dd17ffc2a786
Print the "file" command suggestion in exec_file_locate_attach

currently:
$ gdbserver-7.9 :1234 true &
$ gdb -q -ex 'target remote :1234' # that -q is not relevant here
Remote debugging using :1234
warning: Could not load vsyscall page because no executable was specified
try using the "file" command first.
0x00007ffff7ddcc80 in ?? ()
(gdb) b main
No symbol table is loaded.  Use the "file" command.
Make breakpoint pending on future shared library load? (y or [n]) _

Provide more suggestive message to use the "file" command.

gdb/ChangeLog
2016-04-06  Jan Kratochvil  <jan.kratochvil@redhat.com>
    Pedro Alves  <palves@redhat.com>

* exec.c (exec_file_locate_attach): Print warning for unsupported
target_pid_to_exec_file.
* symfile-mem.c (add_vsyscall_page): Remove the "file" command
message part.
gdb/ChangeLog
gdb/exec.c
gdb/remote.c
gdb/symfile-mem.c
This page took 0.027936 seconds and 4 git commands to generate.