[SERVER-48622] stacktrace_test segfaults with TSAN Created: 05/Jun/20 Updated: 06/Dec/22 |
|
| Status: | Open |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Ryan Egesdahl (Inactive) | Assignee: | Backlog - Service Architecture |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | servicearch-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Assigned Teams: |
Service Arch
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Story Points: | 3 | ||||||||||||||||
| Description |
|
PrintAllThreadStacksTest (specifically, the WithDeadThreads case) fails with a segfault when compiled with TSAN. After some discussion with billy.donahue, we discovered that TSAN has internal threads which may be blocking SIGUSR2, which violates some assumptions the server has about which threads are running and what signals they can receive. It might be a good idea to fix this assumption so we can fully exercise the server with TSAN testing. However, I have disabled the test with TSAN for the time being in |
| Comments |
| Comment by Lauren Lewis (Inactive) [ 21/Dec/21 ] |
|
We haven’t heard back from you in at least 1 year, so I'm going to close this ticket. If this is still an issue for you, please provide additional information and we will reopen the ticket. |
| Comment by Andrew Morrow (Inactive) [ 14/Jul/20 ] |
|
Please note the TSAN bug in |
| Comment by Ryan Egesdahl (Inactive) [ 09/Jun/20 ] |
|
To clarify: while I will be working on a part of this in the sense that I am disabling the feature with TSAN, I think it still needs to be fixed so it can work with TSAN so developers can have their normal debugging workflow when diagnosing TSAN issues. That second part is something I am not working on right now. |