From: "Carsey, Jaben" <jaben.carsey@intel.com>
To: Jeff Westfahl <jeff.westfahl@ni.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Ni, Ruiyu" <ruiyu.ni@intel.com>
Subject: Re: [PATCH v3] ShellPkg/ShellCommandLib: Update DumpHex to print {|}~
Date: Wed, 26 Apr 2017 21:11:47 +0000 [thread overview]
Message-ID: <CB6E33457884FA40993F35157061515C54C0FA40@FMSMSX103.amr.corp.intel.com> (raw)
In-Reply-To: <1493236769-19695-1-git-send-email-jeff.westfahl@ni.com>
That makes sense. When I wrote that I was unsure where to draw the line between which characters to print and which to replace.
Reviewed-by: Jaben Carsey <jaben.carsey@intel.com>
> -----Original Message-----
> From: Jeff Westfahl [mailto:jeff.westfahl@ni.com]
> Sent: Wednesday, April 26, 2017 12:59 PM
> To: edk2-devel@lists.01.org
> Cc: Jeff Westfahl <jeff.westfahl@ni.com>; Ni, Ruiyu <ruiyu.ni@intel.com>;
> Carsey, Jaben <jaben.carsey@intel.com>
> Subject: [edk2][PATCH v3] ShellPkg/ShellCommandLib: Update DumpHex to
> print {|}~
> Importance: High
>
> ASCII characters {|}~ should be printed by DumpHex. The problem is that
> if you have a string like
>
> {xizzy}~{foo|bar}~{quux}
>
> in the dumped data, it will not appear as such in the *-delimited ASCII
> column to the right, but as
>
> .xizzy...foo.bar...quux.
>
> which is less than ideal.
>
> Most of the commit message was inspired by/shamelessly stolen from
> Laszlo's example:
>
> https://lists.01.org/pipermail/edk2-devel/2017-April/010266.html
>
> Cc: Ruiyu Ni <ruiyu.ni@intel.com>
> Cc: Jaben Carsey <jaben.carsey@intel.com>
> Contributed-under: TianoCore Contribution Agreement 1.0
> Signed-off-by: Jeff Westfahl <jeff.westfahl@ni.com>
> Reviewed-by: Laszlo Ersek <lersek@redhat.com>
> ---
> ShellPkg/Library/UefiShellCommandLib/UefiShellCommandLib.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/ShellPkg/Library/UefiShellCommandLib/UefiShellCommandLib.c
> b/ShellPkg/Library/UefiShellCommandLib/UefiShellCommandLib.c
> index a2ebc8f..bd14878 100644
> --- a/ShellPkg/Library/UefiShellCommandLib/UefiShellCommandLib.c
> +++ b/ShellPkg/Library/UefiShellCommandLib/UefiShellCommandLib.c
> @@ -1745,7 +1745,7 @@ DumpHex (
> Val[Index * 3 + 0] = Hex[TempByte >> 4];
> Val[Index * 3 + 1] = Hex[TempByte & 0xF];
> Val[Index * 3 + 2] = (CHAR8) ((Index == 7) ? '-' : ' ');
> - Str[Index] = (CHAR8) ((TempByte < ' ' || TempByte > 'z') ? '.' :
> TempByte);
> + Str[Index] = (CHAR8) ((TempByte < ' ' || TempByte > '~') ? '.' :
> TempByte);
> }
>
> Val[Index * 3] = 0;
> --
> 2.7.4
next prev parent reply other threads:[~2017-04-26 21:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-26 19:59 [PATCH v3] ShellPkg/ShellCommandLib: Update DumpHex to print {|}~ Jeff Westfahl
2017-04-26 21:11 ` Carsey, Jaben [this message]
2017-05-03 13:34 ` Jeff Westfahl
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-list 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=CB6E33457884FA40993F35157061515C54C0FA40@FMSMSX103.amr.corp.intel.com \
--to=devel@edk2.groups.io \
/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