[MDBF-106] More resolution on failures Created: 2020-06-24  Updated: 2022-04-28

Status: Open
Project: MariaDB Foundation Development
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major
Reporter: Vlad Bogolin Assignee: Vlad Bogolin
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
PartOf
is part of MDBF-41 Milestone 5: Desirable fixes Open

 Description   

Suggestions from danblack

1. 'set print frame-arguments all' to a global gdb config file to ensure that structures are expanded in gdb backtraces rather than showing as ... (tip thanks to marko)

2. export UBSAN_OPTIONS=print_stacktrace=1 as global env variable so UBSAN builds have a complete BT of their failures in the mysql error log like MDEV-22387. I haven't seen a UBSAN based build but it will be useful for when one is made

 Comments   
Comment by Daniel Black [ 2022-04-28 ]

gdb execution done in mtr.

Remaining:

  • ulimit of core files lifted where test runs are done. Containers default to 0
  • gdb in containers
  • upload core files as part of saving results and binaries.

UBSAN_OPTIONS might be possible to move to mtr.

addr2line is producing garbage innodb traces. so add --loose-skip-stack-trace MDEV-26949

Generated at Thu Feb 08 03:35:29 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.