Aerospike C Client Crash - SIGSEGV


Hi, I’m getting a crash error after my program starts. Is there someone that had a similar problem ?

[Thread 0x7f9711ada700 (LWP 109228) exited] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7f970a5fb700 (LWP 109233)] heap_remove (less_than=0x7f97203074e0 <timer_less_than>, node=0x7f96cc1ddca8, heap=0x7f96e4000ac8) at ./src/heap-inl.h:196 196 child->left = node->left; (gdb) bt #0 heap_remove (less_than=0x7f97203074e0 <timer_less_than>, node=0x7f96cc1ddca8, heap=0x7f96e4000ac8) at ./src/heap-inl.h:196 #1 uv_timer_stop (handle=handle@entry=0x7f96cc1ddc40) at src/unix/timer.c:97 #2 0x00007f971bed6165 in as_event_stop_timer (cmd=0x7f96cc1ddc40) at src/include/aerospike/as_event_internal.h:396 #3 as_event_response_complete (cmd=0x7f96cc1ddc40) at src/main/aerospike/as_event.c:757 #4 as_event_executor_complete (cmd=cmd@entry=0x7f96cc1ddc40) at src/main/aerospike/as_event.c:850 #5 0x00007f971bebd3ce in as_batch_async_parse_records (cmd=0x7f96cc1ddc40) at src/main/aerospike/aerospike_batch.c:186 #6 0x00007f971bed7585 in as_uv_command_read (stream=0x7f96f800ebd0, nread=, buf=) at src/main/aerospike/as_event_uv.c:325 #7 0x00007f97203047e4 in uv__read (stream=stream@entry=0x7f96f800ebd0) at src/unix/stream.c:1249 #8 0x00007f972030553c in uv__stream_io (loop=, w=0x7f96f800ec58, events=1) at src/unix/stream.c:1316 #9 0x00007f972030a1e8 in uv__io_poll (loop=loop@entry=0x7f96f80008c0, timeout=32663) at src/unix/linux-core.c:400 #10 0x00007f97202fbe88 in uv_run (loop=0x7f96f80008c0, mode=mode@entry=UV_RUN_DEFAULT) at src/unix/core.c:368 #11 0x00007f971bed64ae in as_uv_worker (udata=0x7fffdfaecf20) at src/main/aerospike/as_event_uv.c:160 #12 0x00007f971fa9d184 in start_thread (arg=0x7f970a5fb700) at pthread_create.c:312 #13 0x00007f971e6db37d in clone () at …/sysdeps/unix/sysv/linux/x86_64/clone.S:111


You can find whether other people have a similar problem, or report such a problem at the Github repo aerospike/aerospike-client-c. Include details about your version of the C client, your OS, and reproducible code. That makes a good bug report.


Which C client version are you using?