[SERVER-13956] Add unique build-ids to built binaries on GNU toolchains too old to support gnu build-id. Created: 15/May/14 Updated: 19/Jul/16 Resolved: 12/Jul/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code |
| Affects Version/s: | None |
| Fix Version/s: | 3.3.10 |
| Type: | Improvement | 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 | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Platforms 17 (07/15/16) | ||||||||
| Participants: | |||||||||
| Description |
|
RHEL5 and other older Linux distributions have toolchains too old to add unique build ids to every built binary. This ticket is to amend the build system so that on such systems a post-build step for programs adds a unique id of the same format as GNU build-id tags. This will allow the stack tracer from |
| Comments |
| Comment by Githook User [ 12/Jul/16 ] |
|
Author: {u'username': u'jbreams', u'name': u'Jonathan Reams', u'email': u'jbreams@mongodb.com'}Message: |
| Comment by Jonathan Reams [ 07/Jul/16 ] |
|
In |
| Comment by Andrew Morrow (Inactive) [ 02/Jul/16 ] |
|
It seems like it would be pretty easy to write a script to pull down all the builds from 3.3.9 and check them. Lets do that. |
| Comment by Jonathan Reams [ 27/Jun/16 ] |
|
I believe that with the toolchain v2 all platforms should support gnu build id's since we use the latest version of the linker everywhere. |