-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TID in the files and on the stack trace not matching #872
Comments
The difference is expected as per
The answer to your question depends on how you intend to identify your threads. |
@sergiud I want to look at which thread caused the crash. Is there a way to know that? |
I'm not sure I understand what are you asking given you have two IDs at your disposal. Choose the one that suits your tooling.
This is likely an inconsistency that arose over time. You are welcome to provide a fix. |
@sergiud We have a stack trace of the crash with an ID: 0x36087700. I want to see the log files and see what this thread was doing before crashing. In a multi-threaded env. this can be really helpful.
Which function is preferable: GetTID or pthread_self? I will see if I can fix it. |
For consistency and information gain both functions should be used. |
In the stack trace, we see something like this:
In the files, we see:
I1107 17:38:43.965498 22378 xx.cc:nnn]
22378 is supposed to be the thread id and so is: 0x36087700. I skimmed over the code and seems like 2 different functions are used to compute the values:
(a)
glog/src/signalhandler.cc
Line 211 in a34226c
(b)
glog/src/utilities.cc
Line 259 in f4dd77a
What is the relation between the two? How do I know which TID caused the crash?
The text was updated successfully, but these errors were encountered: