[SERVER-28824] Unhandled hang analyzer exception escapes loop to get threads from each process Created: 17/Apr/17 Updated: 12/Oct/17 Resolved: 08/Aug/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 3.4.9, 3.5.12 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Daniel Gottlieb (Inactive) | Assignee: | Jonathan Abrahams |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Operating System: | ALL | ||||||||||||
| Backport Requested: |
v3.4
|
||||||||||||
| Sprint: | TIG 2017-06-19, TIG 2017-08-21 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 0 | ||||||||||||
| Description |
|
Happened on Solaris as part of an Evergreen task timeout:
|
| Comments |
| Comment by Githook User [ 14/Aug/17 ] | |||||||||||||||
|
Author: {'name': 'Jonathan Abrahams', 'username': 'hptabster', 'email': 'jonathan@mongodb.com'}Message: (cherry picked from commit 324839c0c0c2b294a44d130105797ccdbb3b17a9) | |||||||||||||||
| Comment by Githook User [ 08/Aug/17 ] | |||||||||||||||
|
Author: {'username': 'hptabster', 'email': 'jonathan@mongodb.com', 'name': 'Jonathan Abrahams'}Message: | |||||||||||||||
| Comment by Jonathan Abrahams [ 04/Aug/17 ] | |||||||||||||||
|
It makes sense to trap the exceptions when invoking the debugger and hold them until the end. | |||||||||||||||
| Comment by Max Hirschhorn [ 13/Jul/17 ] | |||||||||||||||
|
jonathan.abrahams, I think we should either ignore the a non-zero return code from the debugger or defer raising an exception until the debugger has finished attaching to all processes. This behavior is preventing jstack from running against both Java VM processes when a Jepsen task times out. | |||||||||||||||
| Comment by Jonathan Abrahams [ 13/Jun/17 ] | |||||||||||||||
|
This was fixed by the upgrade to GDB 7.12.1. | |||||||||||||||
| Comment by Mark Benvenuto [ 27/Apr/17 ] | |||||||||||||||
|
GDB 7.12.1 contains the fix. From https://sourceware.org/gdb/download/ANNOUNCEMENT:
| |||||||||||||||
| Comment by Max Hirschhorn [ 27/Apr/17 ] | |||||||||||||||
|
mark.benvenuto, is there a way to tell if the version of GDB 7.12 in the MongoDB toolchain contains the fix from https://sourceware.org/bugzilla/show_bug.cgi?id=20939? |