From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin-patches@cygwin.com
Subject: Re: [PATCH 2/7] Use matching format for NTSTATUS
Date: Fri, 14 Jan 2022 21:38:14 -0700 [thread overview]
Message-ID: <e79bbaae-e146-e4ad-b16b-0563c7768c33@SystematicSw.ab.ca> (raw)
In-Reply-To: <20220114221018.43941-3-lavr@ncbi.nlm.nih.gov>
See fprintf(3p) POSIX:
# Specifies that the value is to be converted to an alternative form.
...
For x or X conversion specifiers, a non-zero result shall have 0x
(or 0X) prefixed to it.
On 2022-01-14 15:10, Anton Lavrentiev via Cygwin-patches wrote:
> ---
> winsup/cygwin/libc/minires-os-if.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/winsup/cygwin/libc/minires-os-if.c b/winsup/cygwin/libc/minires-os-if.c
> index 666a008de..6e17de0b8 100644
> --- a/winsup/cygwin/libc/minires-os-if.c
> +++ b/winsup/cygwin/libc/minires-os-if.c
> @@ -359,7 +359,7 @@ static void get_registry_dns(res_state statp)
> status = RtlCheckRegistryKey (RTL_REGISTRY_SERVICES, keyName);
> if (!NT_SUCCESS (status))
> {
> - DPRINTF (statp->options & RES_DEBUG, "RtlCheckRegistryKey: status %p\n",
> + DPRINTF (statp->options & RES_DEBUG, "RtlCheckRegistryKey: status 0x%08X\n",
DPRINTF (statp->options & RES_DEBUG, "RtlCheckRegistryKey:
status %#08x\n",
> status);
> return;
> }
> @@ -381,7 +381,7 @@ static void get_registry_dns(res_state statp)
> if (!NT_SUCCESS (status))
> {
> DPRINTF (statp->options & RES_DEBUG,
> - "RtlQueryRegistryValues: status %p\n", status);
> + "RtlQueryRegistryValues: status 0x%08x\n", status);
"RtlQueryRegistryValues: status %#08x\n", status);
> return;
> }
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]
next prev parent reply other threads:[~2022-01-15 4:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-14 22:10 Cygwin: A few fixes for local resolver Anton Lavrentiev
2022-01-14 22:10 ` [PATCH 1/7] Fix format specifier for wide-char string Anton Lavrentiev
2022-01-14 22:10 ` [PATCH 2/7] Use matching format for NTSTATUS Anton Lavrentiev
2022-01-15 4:38 ` Brian Inglis [this message]
2022-01-15 19:04 ` [EXTERNAL] " Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2022-01-15 22:38 ` Brian Inglis
2022-01-16 0:20 ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2022-01-14 22:10 ` [PATCH 3/7] Debug output to show both IP and port # in native b.o., a few little cosmetic improvements for consistency Anton Lavrentiev
2022-01-17 10:39 ` Corinna Vinschen
2022-01-17 10:44 ` Corinna Vinschen
2022-01-14 22:10 ` [PATCH 4/7] Process options forward (not backwards) Anton Lavrentiev
2022-01-14 22:10 ` [PATCH 5/7] Format consitency for Windows errors Anton Lavrentiev
2022-01-14 22:10 ` [PATCH 6/7] Message consistency Anton Lavrentiev
2022-01-14 22:10 ` [PATCH 7/7] Added processing of AAAA records Anton Lavrentiev
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=e79bbaae-e146-e4ad-b16b-0563c7768c33@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin-patches@cygwin.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).