From: Luis Machado <lgustavo@codesourcery.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Add -verify option to load command
Date: Fri, 06 Jan 2017 18:30:00 -0000 [thread overview]
Message-ID: <51235c70-a165-37de-c6f1-e54e17d72213@codesourcery.com> (raw)
In-Reply-To: <838tqocats.fsf@gnu.org>
On 01/06/2017 12:17 PM, Eli Zaretskii wrote:
>> From: Luis Machado <lgustavo@codesourcery.com>
>> Date: Fri, 6 Jan 2017 10:41:52 -0600
>>
>> --- a/gdb/doc/gdb.texinfo
>> +++ b/gdb/doc/gdb.texinfo
>> @@ -19592,7 +19592,7 @@ Show the current status of displaying communications between
>> @table @code
>>
>> @kindex load @var{filename}
>> -@item load @var{filename}
>> +@item load @var{filename} [-verify]
>> @anchor{load}
>> Depending on what remote debugging facilities are configured into
>> @value{GDBN}, the @code{load} command may be available. Where it exists, it
>> @@ -19614,6 +19614,9 @@ specifies a fixed address.
>> Depending on the remote side capabilities, @value{GDBN} may be able to
>> load programs into flash memory.
>>
>> +The optional @code{-verify} argument enables verification of the data that was
>> +loaded to the target's memory.
>
> I think the manual should explain what "verification" means in this
> context.
>
> Thanks.
>
Something along the lines of...
"GDB will make sure all the memory regions that were written to the
target's memory have their correct values, otherwise an error will be
issued."?
Should i go even further to explain how the comparison is made?
next prev parent reply other threads:[~2017-01-06 18:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-06 16:42 Luis Machado
2017-01-06 18:17 ` Eli Zaretskii
2017-01-06 18:30 ` Luis Machado [this message]
2017-01-07 7:53 ` Eli Zaretskii
2017-01-06 19:17 ` Simon Marchi
2017-01-06 19:33 ` Luis Machado
2017-01-06 19:59 ` Simon Marchi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51235c70-a165-37de-c6f1-e54e17d72213@codesourcery.com \
--to=lgustavo@codesourcery.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox