Operational Defect Database

BugZero found this defect 2506 days ago.

MongoDB | 374715

[SERVER-28824] Unhandled hang analyzer exception escapes loop to get threads from each process

Last update date:

10/12/2017

Affected products:

MongoDB Server

Affected releases:

No affected releases provided.

Fixed releases:

3.4.9

3.5.12

Description:

Info

Happened on Solaris as part of an Evergreen task timeout: [2017/04/14 18:04:33.677] terminate called after throwing an instance of 'gdb_exception_RETURN_MASK_ERROR' [2017/04/14 18:04:34.794] 200 Thread 166 [2017/04/14 18:04:35.043] Bad exit code -6 [2017/04/14 18:04:35.043] Traceback (most recent call last): [2017/04/14 18:04:35.043] File "buildscripts/hang_analyzer.py", line 732, in <module> [2017/04/14 18:04:35.044] main() [2017/04/14 18:04:35.044] File "buildscripts/hang_analyzer.py", line 700, in main [2017/04/14 18:04:35.044] options.dump_core and check_dump_quota(max_dump_size_bytes, dbg.get_dump_ext())) [2017/04/14 18:04:35.044] File "buildscripts/hang_analyzer.py", line 381, in dump_info [2017/04/14 18:04:35.044] logger) [2017/04/14 18:04:35.044] File "buildscripts/hang_analyzer.py", line 56, in call [2017/04/14 18:04:35.044] raise Exception() [2017/04/14 18:04:35.044] Exception [2017/04/14 18:04:35.084] Command failed: exit status 1

Top User Comments

xgen-internal-githook commented on Mon, 14 Aug 2017 13:01:31 +0000: Author: {'name': 'Jonathan Abrahams', 'username': 'hptabster', 'email': 'jonathan@mongodb.com'} Message: SERVER-28824 Trap debugger excptions in hang analyzer and display at end for all processes (cherry picked from commit 324839c0c0c2b294a44d130105797ccdbb3b17a9) Branch: v3.4 https://github.com/mongodb/mongo/commit/01f3279e039f610a99ef84238ca49498c716ee14 xgen-internal-githook commented on Tue, 8 Aug 2017 15:33:56 +0000: Author: {'username': 'hptabster', 'email': 'jonathan@mongodb.com', 'name': 'Jonathan Abrahams'} Message: SERVER-28824 Trap debugger excptions in hang analyzer and display at end for all processes Branch: master https://github.com/mongodb/mongo/commit/324839c0c0c2b294a44d130105797ccdbb3b17a9 jonathan.abrahams commented on Fri, 4 Aug 2017 14:17:08 +0000: It makes sense to trap the exceptions when invoking the debugger and hold them until the end. max.hirschhorn@10gen.com commented on Thu, 13 Jul 2017 14:21:44 +0000: 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. jonathan.abrahams commented on Tue, 13 Jun 2017 19:23:00 +0000: This was fixed by the upgrade to GDB 7.12.1. mark.benvenuto commented on Thu, 27 Apr 2017 13:56:03 +0000: GDB 7.12.1 contains the fix. From https://sourceware.org/gdb/download/ANNOUNCEMENT: GDB 7.12.1 brings the following fixes and enhancements over GDB 7.12:   * PR tdep/20682 (aarch64 regression: gdb.cp/nextoverthrow.exp) * PR server/20733 (Failed to build aarch64_be-linux-gnu GDBserver) * PR tdep/20953 (GDB crashes after "set architecture rl78") * PR tdep/20954 (GDB crashes if "set architecture rx") * PR tdep/20955 (GDB internal error in cris-tdep.c) * PR build/20712 (gdb 7.12+ doesn't build as C++ on Solaris) * PR breakpoint/20653 (string_to_explicit_location has some weird code) * PR build/20753 (MinGW compilation errors due to strcasecmp) * PR gdb/20977 (GDB exception handling is broken on i686-w64-mingw32) * PR python/21048 (backtrace is broken on i686) * PR sim/20808 (mips sim build fails due to undefined SD/CPU variables) * PR sim/20809 (mips sim build fails for r3900 cpus) * PR gdb/20939 (GDB aborts if there is an error in disassembly) max.hirschhorn@10gen.com commented on Thu, 27 Apr 2017 05:55:54 +0000: 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?

Additional Resources / Links

Share:

BugZero Risk Score

Coming soon

Status

Closed

Have you been affected by this bug?

cost-cta-background

Do you know how much operational outages are costing you?

Understand the cost to your business and how BugZero can help you reduce those costs.

Discussion

Login to read and write comments.

Have you ever...

had your data corrupted from a

VMware

bug?

Search:

...