This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH 5/7] Implement remote_pid_to_exec_file using qXfer:exec-file:read
- From: Doug Evans <xdje42 at gmail dot com>
- To: Eli Zaretskii <eliz at gnu dot org>
- Cc: Gary Benson <gbenson at redhat dot com>, gdb-patches at sourceware dot org
- Date: Mon, 06 Apr 2015 10:00:08 -0700
- Subject: Re: [PATCH 5/7] Implement remote_pid_to_exec_file using qXfer:exec-file:read
- Authentication-results: sourceware.org; auth=none
- References: <1427887341-31819-1-git-send-email-gbenson at redhat dot com> <1427887341-31819-6-git-send-email-gbenson at redhat dot com> <834mozsxtq dot fsf at gnu dot org>
Eli Zaretskii <eliz@gnu.org> writes:
>> Date: Wed, 1 Apr 2015 12:22:19 +0100
>>
>> +qXfer:exec-file:read
>> + Return the pathname of the file that was executed to create a
> ^^^^^^^^^^^^^^^^^^^^^^^^
> "the name of the file"
>
> OK with this change.
>
>> +@item qXfer:exec-file:read:@var{annex}:@var{offset},@var{length}
>> +@anchor{qXfer executable filename read}
>> +Return the pathname of the file that was executed to create a process
> ^^^^^^^^^^^^^^^^^^^^^^^^
> Likewise.
>
> Otherwise, the documentation parts are OK.
"the name of the file" is ambiguous though.
Is it the full path name of the file? Or the base name?
Can the target choose? [I hope not.]
IWBN to have more clarity here.
While I realize "path" is a term associated with directories
(paths in which to find files), "full path name" is in common
use for complete/absolute file names.