[SERVER-66539] libunwind stack trace error on arm64 Created: 18/May/22  Updated: 11/Jul/22  Resolved: 11/Jul/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Josef Ahmad Assignee: Daniel Moody
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Operating System: ALL
Sprint: Dev Platform 2022-06-13, Dev Platform 2022-06-27, Dev Platform 2022-07-11
Participants:

 Description   

Spotted in an integration test:

E  CONTROL  31430   [conn46] "Error collecting stack trace","attr":{"error":"unw_get_proc_name(FFFF9554E668): unspecified (general) error\nunw_get_proc_name(FFFF9554E668): unspecified (general) error\n"} 

Related, this error appears to also inhibit the generation of a core dump in our integration tests.



 Comments   
Comment by Andrew Morrow (Inactive) [ 18/May/22 ]

I'm not sure if this error is inhibiting cores or whether the system is misconfigured (ulimits, core pattern, etc.). It could be one or both.

Generated at Thu Feb 08 06:05:43 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.