From: Joel Brobecker <brobecker@adacore.com>
To: Tristan Gingold <gingold@adacore.com>
Cc: gdb-patches ml <gdb-patches@sourceware.org>
Subject: Re: [RFA]: windows: always use %x to print thread id
Date: Fri, 15 Jan 2010 06:35:00 -0000 [thread overview]
Message-ID: <20100115063523.GB2786@adacore.com> (raw)
In-Reply-To: <476393A3-DFE0-487B-9976-6F7F9939E1E5@adacore.com>
> also this is a not for the user, tid in messages displayed by 'set
> debugevents 1' are often in decimal and sometimes in hexadecimal. But
> windows_pid_to_str prints the tid in hexa. As this is slightly
> confusing, with this patch the tid is always printed in hexadecimal.
I think this makes sense, and since Chris hasn't answered yet:
> 2010-01-12 gingold <gingold@adacore.com>
>
> * windows-nat.c (windows_continue): Use %x to print thread id.
> (get_windows_debug_event): Ditto.
This is OK.
--
Joel
next prev parent reply other threads:[~2010-01-15 6:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-12 15:55 Tristan Gingold
2010-01-15 6:35 ` Joel Brobecker [this message]
2010-01-15 19:21 ` Christopher Faylor
2010-01-25 10:55 ` Tristan Gingold
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=20100115063523.GB2786@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=gingold@adacore.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