From: Supreeth Venkatesh <supreeth.venkatesh@arm.com>
To: Lokesh B V <lokesh.bv@arm.com>, edk2-devel@lists.01.org
Subject: Re: [PATCH 2/2] [edk2-test][PATCH v2] SctPkg/Tools: Fix incorrect line ending detection by GenBin tool
Date: Tue, 27 Nov 2018 21:12:49 -0600 [thread overview]
Message-ID: <46d12bf2ce3f55cf0c5de425dfe079ca4a0c3f49.camel@arm.com> (raw)
In-Reply-To: <1543341035-22358-1-git-send-email-lokesh.bv@arm.com>
Same general comments apply (given in first one in the series).
On Tue, 2018-11-27 at 23:20 +0530, Lokesh B V wrote:
> Some windows editors uses "\r\n" for line feed. While processing uefi
> testcase
> info file, the GenBin tool logic to skip line feed doesn't consider
> the presence
> of carraige return(\r) in line feed. So this results in incorrect
Please fix the commit message with "carriage return" (same comment as
given by Philippe)
> format error.
>
> Cc: Supreeth Venkatesh <supreeth.venkatesh@arm.com>
> Contributed-under: TianoCore Contribution Agreement 1.1
> Signed-off-by: Lokesh B V <lokesh.bv@arm.com>
>
> Signed-off-by: Lokesh B V <lokesh.bv@arm.com>
> ---
> uefi-sct/SctPkg/Tools/Source/GenBin/GenBin.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/uefi-sct/SctPkg/Tools/Source/GenBin/GenBin.c b/uefi-
> sct/SctPkg/Tools/Source/GenBin/GenBin.c
> index 61bb35b..4eaefcc 100644
> --- a/uefi-sct/SctPkg/Tools/Source/GenBin/GenBin.c
> +++ b/uefi-sct/SctPkg/Tools/Source/GenBin/GenBin.c
> @@ -2,6 +2,7 @@
>
> Copyright 2006 - 2010 Unified EFI, Inc.<BR>
> Copyright (c) 2010 Intel Corporation. All rights reserved.<BR>
> + Copyright (c) 2018 ARM Ltd. All rights reserved.<BR>
>
> This program and the accompanying materials
> are licensed and made available under the terms and conditions of
> the BSD License
> @@ -176,6 +177,7 @@ Trim (
> for (Index1 = 0; Index1 < Length; Index1++) {
> if ((String[Index1] != ' ' ) &&
> (String[Index1] != '\t') &&
> + (String[Index1] != '\r') &&
> (String[Index1] != '\n')) {
> break;
> }
This Trim function is ridden with bugs. Use the linux kernel
implementation to avoid bugs. Lets fix this properly. something like
below.
char *
Trim (
char *s
)
{
size_t size;
char *end;
size = strlen(s);
if (!size)
return s;
end = s + size - 1;
while (end >= s && isspace(*end))
end--;
*(end + 1) = '\0';
while (*s && isspace(*s))
s++;
return s;
}
> @@ -193,6 +195,7 @@ Trim (
> for (Index1 = 0; Index1 < Length; Index1++) {
> if ((String[Length - 1 - Index1] != ' ' ) &&
> (String[Length - 1 - Index1] != '\t') &&
> + (String[Length - 1 - Index1] != '\r') &&
> (String[Length - 1 - Index1] != '\n')) {
> break;
> }
Finally, Getline function should be altered as below to properly skip
empty lines and comment lines like below (or similar).
for ( ; ; ) {
//
// Get a string from the profile
//
Result = fgets (String, MAX_LINE_LENGTH, Profile);
if (Result == NULL) {
return -1;
}
//
// Remove the beginning and ending space characters
//
String = Trim (Result);
//
// Skip the empty line and comment line
//
if ((String[0] == '\0') ||
(String[0] == '#' )) {
continue;
}
(*LineNo)++;
}
prev parent reply other threads:[~2018-11-28 3:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-27 17:50 [PATCH 2/2] [edk2-test][PATCH v2] SctPkg/Tools: Fix incorrect line ending detection by GenBin tool Lokesh B V
2018-11-28 3:12 ` Supreeth Venkatesh [this message]
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=46d12bf2ce3f55cf0c5de425dfe079ca4a0c3f49.camel@arm.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