Repository navigation
SegFault in benchmark #504
Description
> Do you understand why the call give the segfault?
Segfault is due to some implementation detail of the CXXGraph object. Has to be debug elsewhere; however this fix identifies the buggy tests and comment them out (which should be tracked elsewhere) and propose a fix to re-enable benchmarking tests.
Originally posted by @ai-mannamalai in #503 (comment)
Activity
JustCallMeRay commentedon Jul 14, 2025
Shall we start running the tests with ASAN on the pipeline? This would reduce the chances it happens again but is no guarantee. Running the benchmarks on pipeline would also help and/or with ASAN also (but maybe set zero repeats assuming google benchmark can do that at runtime)
For some context: A segmentation fault is where a process asks for memory (a segment of memory) it does not own. ASAN forces every read and write of memory to go through some checks that force that address to be valid. It also provides some information on what failed and why
ZigRazor commentedon Jul 16, 2025
@JustCallMeRay tests with ASAN could be useful but obviously can alter execution context so the problem could not happens again.
A try is possible, we can see somenthing strange