[CASSANDRA-19565] SIGSEGV on Cassandra v4.1.4

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 4.0.14, 4.1.6, 5.0-beta2, 5.0, 5.1
• Component/s: Packaging
• Bug Category: Correctness
• Severity: Normal
• Complexity: Normal
• Discovered By: User Report
• Platform: All
• Since Version: NA

Source Control Link

https://github.com/apache/cassandra/commit/f12f928dee2291d0ca98a20c788d545e6ffb623b

Test and Documentation Plan

run packaging CI

• Assignee: Brandon Williams Assign to me
• Reporter: Thomas De Keulenaer

Authors

Brandon Williams

Reviewers

Berenguer Blasi

• Created: 17/Apr/24 07:52
• Updated: 06/May/24 13:44
• Resolved: 06/May/24 13:44

Description

Hello,

Since upgrading to v4.1. we cannat run CAssandra any more. Each start immediately crashes:
{{Apr 17 08:58:34 SVALD108 cassandra[1116450]: # A fatal error has been detected by the Java Runtime Environment:
Apr 17 08:58:34 SVALD108 cassandra[1116450]: # SIGSEGV (0xb) at pc=0x00007fccaab4d152, pid=1116450, tid=1116451}}

I have added the log from the coe dump.

This issue is perhaps related to https://davecturner.github.io/2021/08/30/seven-year-old-segfault.html ?

Issue Links

• is related to: CASSANDRA-18050 Update JNA
• relates to: CASSANDRA-19570 Allow setting LIBFFI_TMPDIR
• links to: CASSANDRA-19565-4.1