public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: Andrew Fish <afish@apple.com>, Jeff Fan <jeff.fan@intel.com>,
	Feng Tian <feng.tian@intel.com>,
	Mike Kinney <michael.d.kinney@intel.com>
Cc: "edk2-devel@lists.01.org" <edk2-devel@ml01.01.org>
Subject: Re: [PATCH] UefiCpuPkg/SecCore: Use %x to print stack information
Date: Tue, 15 Nov 2016 19:11:20 +0100	[thread overview]
Message-ID: <4804ad49-f8d9-90d5-21f5-7b44d2229b95@redhat.com> (raw)
In-Reply-To: <D87FC9B6-271F-4133-A0C7-8B5CD6285738@apple.com>

On 11/15/16 18:47, Andrew Fish wrote:
> 
>> On Nov 15, 2016, at 8:59 AM, Laszlo Ersek <lersek@redhat.com
>> <mailto:lersek@redhat.com>> wrote:
>>
>> On 11/15/16 09:32, Jeff Fan wrote:
>>> SecCoreData->StackBase is VOID * type and SecCoreData->StackSize is
>>> UINTN type.
>>> We should use %x to dump their value instead of %lx.
>>>
>>> Cast pointer type to UINTN before print it.
>>>
>>> Cc: Feng Tian <feng.tian@intel.com <mailto:feng.tian@intel.com>>
>>> Cc: Michael D Kinney <michael.d.kinney@intel.com
>>> <mailto:michael.d.kinney@intel.com>>
>>> Contributed-under: TianoCore Contribution Agreement 1.0
>>> Signed-off-by: Jeff Fan <jeff.fan@intel.com <mailto:jeff.fan@intel.com>>
>>> ---
>>> UefiCpuPkg/SecCore/SecMain.c | 4 ++--
>>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/UefiCpuPkg/SecCore/SecMain.c b/UefiCpuPkg/SecCore/SecMain.c
>>> index 2ebbc22..4d08f48 100644
>>> --- a/UefiCpuPkg/SecCore/SecMain.c
>>> +++ b/UefiCpuPkg/SecCore/SecMain.c
>>> @@ -239,9 +239,9 @@ SecStartupPhase2(
>>>
>>>   DEBUG ((
>>>     DEBUG_INFO,
>>> -    "%a() Stack Base: 0x%lx, Stack Size: 0x%lx\n",
>>> +    "%a() Stack Base: 0x%x, Stack Size: 0x%x\n",
>>>     __FUNCTION__,
>>> -    SecCoreData->StackBase,
>>> +    (UINTN) SecCoreData->StackBase,
>>>     SecCoreData->StackSize
>>>     ));
>>>
>>>
>>
>> Not disagreeing, just mentioning for completeness: we can also use %p
>> for printing (VOID*) directly.
>>
> 
> %x is sizeof(int) not sizeof(UINTN)?

Sigh, you are correct, of course. "%x" is not portable for printing UINTN.

In fact we recently discussed just that:

  [edk2] What is the right way to print a UINTN?

  https://lists.01.org/pipermail/edk2-devel/2016-September/002091.html

(There seem to be issues with my focus / attention recently... This is
now the second near-trivial issue I've missed in a couple of days. :( I
guess I should get more sleep.)

> So it seems %p would be more
> correct? Or we should just use UINT32 if that is what is intended. 
> 
> https://github.com/tianocore/edk2/blob/master/MdePkg/Include/Library/PrintLib.h#L80
> 
> 	- x
> 	- The argument is an unsigned hexadecimal number. The characters used
> are 0..9 and
> 	A..F. If the flag 'L' is not specified, then the argument is assumed
> 	to be size int. This does not follow ANSI C.
> 

Right, %p is the most direct choice.

Thank you Andrew!
Laszlo



  reply	other threads:[~2016-11-15 18:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-15  8:32 [PATCH] UefiCpuPkg/SecCore: Use %x to print stack information Jeff Fan
2016-11-15  8:37 ` Tian, Feng
2016-11-15 16:59 ` Laszlo Ersek
2016-11-15 17:47   ` Andrew Fish
2016-11-15 18:11     ` Laszlo Ersek [this message]
2016-11-15 18:33       ` Andrew Fish
2016-11-16  1:01     ` Fan, Jeff

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=4804ad49-f8d9-90d5-21f5-7b44d2229b95@redhat.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