You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Brian Geffon (JIRA)" <ji...@apache.org> on 2011/08/19 15:18:27 UTC
[jira] [Updated] (TS-925) Consider switching from integer thread
IDs to hex thread IDs
[ https://issues.apache.org/jira/browse/TS-925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Geffon updated TS-925:
----------------------------
Description:
Integer thread IDs are rarely of any use...please consider switching to hex as GDB and Valgrind both output threads in hex.
was:
Integer thread IDs are rarely of any use...please consider switching to hex as GDB and Valgrind both output threads in hex.
--- lib/ts/Diags.cc 2011-08-16 13:32:12.982036370 -0700
+++ lib/ts/Diags.cc 2011-08-19 05:21:42.036238573 -0700
@@ -211,7 +211,7 @@
// add the thread id
pthread_t id = pthread_self();
- end_of_format += snprintf(end_of_format, sizeof(format_buf), "{%" PRIu64 "} ", (uint64_t) id);
+ end_of_format += snprintf(end_of_format, sizeof(format_buf), "{0x%" PRIx64 "} ", (uint64_t) id);
////////////////////////////////
// start with the user prefix //
> Consider switching from integer thread IDs to hex thread IDs
> ------------------------------------------------------------
>
> Key: TS-925
> URL: https://issues.apache.org/jira/browse/TS-925
> Project: Traffic Server
> Issue Type: Improvement
> Components: Logging
> Reporter: Brian Geffon
> Priority: Trivial
>
> Integer thread IDs are rarely of any use...please consider switching to hex as GDB and Valgrind both output threads in hex.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira