[SERVER-58946] Toolchain gcc-generated debug symbols may be malformed Created: 29/Jul/21 Updated: 08/Jan/23 Resolved: 27/Dec/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Robert Guo (Inactive) | Assignee: | Alex Neben |
| Resolution: | Done | Votes: | 0 |
| Labels: | post-v4-toolchain | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Server Development Platform
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Dev Platform 2021-08-23, Dev Platform 2021-09-20, Dev Platform 2021-10-04, Dev Platform 2021-10-18, Dev Platform 2021-11-29 | ||||
| Participants: | |||||
| Description |
|
The toolchain gcc generated debug symbols can't be read entirely by the toolchain's llvm-symbolizer; there are line numbers missing and maybe other issues. This is possibly only affecting statically linked binaries as some shared library builds and possibly only mongod. Static mongos and shared libraries seem to be fine. Using llvm-symbolizer-10 and above works. Drew tried 10 and I tried 12. Copying some of Drew's research from Slack for context: Running various versions of llvm-symbolizer
Checking the debug symbols format with dwarfdump:
readelf seems to work for both mongod and mongos with both showing debug symbols and source files. |
| Comments |
| Comment by Alex Neben [ 27/Dec/22 ] | ||||||||||||||
|
Feel free to reopen if there is something I missed or am not understanding. | ||||||||||||||
| Comment by Alex Neben [ 27/Dec/22 ] | ||||||||||||||
|
| ||||||||||||||
| Comment by Alex Neben [ 27/Dec/22 ] | ||||||||||||||
| ||||||||||||||
| Comment by Alex Neben [ 27/Dec/22 ] | ||||||||||||||
|
dwarfdump is still returning some errors in v4 but llvm-symbolizer seems to be working better with an optimized clang build. I am not sure what else to do as part of this ticket so I am going to close it. |