[SERVER-19157] hang_analyzer script should use the version of gdb from the the toolchain Created: 26/Jun/15 Updated: 05/Feb/16 Resolved: 30/Jun/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Build |
| Affects Version/s: | None |
| Fix Version/s: | 3.1.6 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Andy Schwerin | Assignee: | Jonathan Reams |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Steps To Reproduce: | Write a c++ unit test that sleeps for several hours. |
| Sprint: | Build 5 06/26/16, Build 6 07/17/15 |
| Participants: |
| Description |
|
The hang analyzer script finds gdb in the path, and our evergreen configuration doesn't add the mongodb toolchain to the path, so we end up running the gdb from /usr/bin. On the Linux64 build variant, gdb is too old to read the debug information from our tool chain, so the hang analyzer produces useless output. We should change either evergreen.yml or the hang analyzer to use the appropriate gdb for the toolchain. |
| Comments |
| Comment by Githook User [ 30/Jun/15 ] |
|
Author: {u'username': u'jbreams', u'name': u'Jonathan Reams', u'email': u'jbreams@mongodb.com'}Message: |