This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH 3/7] Use gdb_sysroot for main executable on attach
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Gary Benson <gbenson at redhat dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Wed, 01 Apr 2015 17:52:57 +0300
- Subject: Re: [PATCH 3/7] Use gdb_sysroot for main executable on attach
- Authentication-results: sourceware.org; auth=none
- References: <1427887341-31819-1-git-send-email-gbenson at redhat dot com> <1427887341-31819-4-git-send-email-gbenson at redhat dot com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> From: Gary Benson <gbenson@redhat.com>
> Date: Wed, 1 Apr 2015 12:22:17 +0100
>
> +* Paths specified by "set sysroot" will be prepended to the path of
> + the main executable when attaching to already-running processes
> + (local and remote) if the path of the main executable is reported
> + to GDB as absolute by the operating system.
Please don't use "path" when you really mean "file name".
OK with that fixed.
> +shared library paths will be prefixed with @var{path}; many runtime
> +loaders store the absolute paths to the shared library in the target
> +program's memory. When attaching to already-running processes, their
> +paths will be prefixed with @var{path} if reported to @value{GDBN} as
> +absolute by the operating system. If you use @code{set sysroot} to
> +find executables and shared libraries, they need to be laid out in
> +the same way that they are on the target, with e.g.@: a @file{/bin},
> +@file{/lib} and @file{/usr/lib} hierarchy under @var{path}.
Same here. (Yes, I know that the previous text also used "path").
Thanks.