https://bugs.kde.org/show_bug.cgi?id=449838
Bug ID: 449838 Summary: sigsegv liburing the 'impossible' happened: Product: valgrind Version: 3.18.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: memcheck Assignee: jsew...@acm.org Reporter: vbextr...@hotmail.com Target Milestone: --- SUMMARY *** i was trying to test my software linking liburing but valgrind segfault. probably this is a problem VgTs_Runnable syscall 425 (lwpid 1181013) ==1181013== at 0x4AE418D: syscall (in /usr/lib/libc-2.33.so) LOG *** $ valgrind --undef-value-errors=no --tool=memcheck --leak-check=yes --show-reachable=yes --num-callers=20 --track-fds=yes ./notstd -i ==1181013== Memcheck, a memory error detector ==1181013== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==1181013== Using Valgrind-3.18.1 and LibVEX; rerun with -h for copyright info ==1181013== Command: ./nostd -i ==1181013== info file.c[ 199]:{0x4BB8800} f_begin():: deadpoll flags:0x1 info memory.c[ 326]:{0x4BB8800} mem_alloc():: allocate 248, extend 1, total 256, align 8, offset 0, real 0x4bbc040, addr 0x4bbc048 info memory.c[ 85]:{0x4BB8800} mem_header_page_alloc():: info memory.c[ 71]:{0x4BB8800} mem_page_alloc():: 3 info memory.c[ 113]:{0x4BB8800} mem_header_new():: new:0x4853fc8 next:0x4853f90 info memory.c[ 340]:{0x4BB8800} mem_alloc():: header address:0x4853fc8 --1181013-- VALGRIND INTERNAL ERROR: Valgrind received a signal 11 (SIGSEGV) - exiting --1181013-- si_code=1; Faulting address: 0x1000; sp: 0x1002c8dc38 valgrind: the 'impossible' happened: Killed by fatal signal host stacktrace: ==1181013== at 0x58040C66: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) ==1181013== by 0x5804EA90: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) ==1181013== by 0x5809EEFB: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) ==1181013== by 0x58117E09: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) ==1181013== by 0x5809CF3A: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) ==1181013== by 0x5809D5CD: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) ==1181013== by 0x58098E02: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) ==1181013== by 0x5809AEE7: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) ==1181013== by 0x580E40F0: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) sched status: running_tid=1 Thread 1: status = VgTs_Runnable syscall 425 (lwpid 1181013) ==1181013== at 0x4AE418D: syscall (in /usr/lib/libc-2.33.so) ==1181013== by 0x49C5EA5: ??? (in /usr/lib/liburing.so.2.1.0) ==1181013== by 0x49C5478: io_uring_queue_init_params (in /usr/lib/liburing.so.2.1.0) ==1181013== by 0x49C5528: io_uring_queue_init (in /usr/lib/liburing.so.2.1.0) ==1181013== by 0x126027: deadpoll_new (deadpoll.c:122) ==1181013== by 0x10B7CE: f_begin (file.c:200) ==1181013== by 0x1278CC: __libc_csu_init (in /home/vbextreme/Project/c/notstd/build/nostd) ==1181013== by 0x4A12AB0: (below main) (in /usr/lib/libc-2.33.so) client stack range: [0x1FFEFFD000 0x1FFF000FFF] client SP: 0x1FFF000458 valgrind stack range: [0x1002B8E000 0x1002C8DFFF] top usage: 8656 of 1048576 Note: see also the FAQ in the source distribution. It contains workarounds to several common problems. In particular, if Valgrind aborted or crashed after identifying problems in your program, there's a good chance that fixing those problems will prevent Valgrind aborting or crashing, especially if it happened in m_mallocfree.c. If that doesn't help, please report this bug to: www.valgrind.org In the bug report, send all the above text, the valgrind version, and what OS and version you are using. Thanks. SOFTWARE/OS VERSIONS Arch linux Linux arci 5.16.4-arch1-1 #1 SMP PREEMPT Sat, 29 Jan 2022 19:08:13 +0000 x86_64 GNU/Linux -- You are receiving this mail because: You are watching all bug changes.