[SERVER-58863] make mongosymb robust to missing "b" and other symbolizer improvements Created: 26/Jul/21  Updated: 29/Oct/23  Resolved: 29/Jul/21

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: 5.1.0-rc0

Type: Improvement Priority: Major - P3
Reporter: Robert Guo (Inactive) Assignee: Robert Guo (Inactive)
Resolution: Fixed Votes: 0
Labels: tig-symbolizer
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File keyerror.log    
Issue Links:
Duplicate
is duplicated by SERVER-58850 Fix symbolizer rerun Closed
is duplicated by SERVER-58839 cache multiversion download in the bu... Closed
Backwards Compatibility: Fully Compatible
Sprint: STM 2021-08-09
Participants:
Story Points: 0

 Description   

segfaults may have a missing b field. mongosymb.py should be smart enough to ignore it.

See this snippet from convo on Slack.

I’m running like this: python buildscripts/resmoke.py symbolize -t mongodb_mongo_v5.0_enterprise_rhel_80_64_bit_dynamic_required_display_jstestfuzz_concurrent_replication_1928c8d20941bdaf094507d0b1616ca58d530330_21_07_20_19_56_18 < backtrace.log

backtrace.log is attached.

This is the problematic line:

{"a":"557019C40800"}

 Comments   
Comment by Vivian Ge (Inactive) [ 06/Oct/21 ]

Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you!

Comment by Robert Guo (Inactive) [ 29/Jul/21 ]

acm for the VDSO issue, should I file a SERVER ticket for Service Arch or do you know if missing "b" is the expected behavior?

Comment by Githook User [ 29/Jul/21 ]

Author:

{'name': 'Robert Guo', 'email': 'robert.guo@mongodb.com'}

Message: SERVER-58863 fix symbolizer rerun error, missing frame info, and move multiversion download cache dir to build
Branch: master
https://github.com/mongodb/mongo/commit/a4b5e8e8c198d3e7d59c76996613b322872af186

Comment by Robert Guo (Inactive) [ 27/Jul/21 ]

Seems plausible, and consistent with a segfault missing the base address.

Comment by Andrew Morrow (Inactive) [ 27/Jul/21 ]

Probably for base.

Comment by Robert Guo (Inactive) [ 27/Jul/21 ]

acm Not familiar with the origin or the significance of the letter "b" as the field name, but its value should correspond to ELF's sh_addr.

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