[SERVER-45218] stacktrace: libunwind steps should be bounded Created: 18/Dec/19 Updated: 29/Oct/23 Resolved: 18/Dec/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code |
| Affects Version/s: | 4.3 Required |
| Fix Version/s: | 4.3.3 |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Billy Donahue | Assignee: | Billy Donahue |
| Resolution: | Fixed | 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: | see HELP-12717
|
| Sprint: | Dev Tools 2019-12-30 |
| Participants: |
| Description |
|
While investigating a deep stack (HELP-12717), we found that the libunwind printStackTrace implementation was doing its job and trying to give as much information as possible, but unfortunately this fills up the log statement 100k limit with just the raw instruction addrs, so all the good stuff in the stack trace is truncated. This is no good. Easiest fix is to just not use libunwind's cursor steps, and just always do a rawBacktrace. |
| Comments |
| Comment by Githook User [ 18/Dec/19 ] |
|
Author: {'name': 'Billy Donahue', 'email': 'billy.donahue@mongodb.com', 'username': 'BillyDonahue'}Message: |
| Comment by Billy Donahue [ 18/Dec/19 ] |