https://bugs.kde.org/show_bug.cgi?id=420682
David Sloan <david.sl...@eideticom.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |david.sl...@eideticom.com
--- Comment #1 from David Sloan <david.sl...@eideticom.com> ---
I have hit the same bug on Ubuntu 24.04 running valgrind version 3.22.0, and
did not see a fix in git.
Steps to reproduce:
missing-syscall.c
```C
#include <assert.h>
#include <fcntl.h>
#include <libaio.h>
#include <unistd.h>
int main()
{
const char *msg = "hello world\n";
struct iocb iocb = {};
struct io_event event;
io_context_t ctx = 0;
struct iocb *iocbp;
int rc, fd;
rc = io_setup(1, &ctx);
assert(rc == 0);
fd = open("test.txt", O_CREAT | O_RDWR, 0666);
assert(fd >= 0);
io_prep_pwrite(&iocb, fd, (void *)msg, 12, 0);
iocbp = &iocb;
rc = io_submit(ctx, 1, &iocbp);
assert(rc == 1);
rc = io_getevents(ctx, 1, 1, &event, NULL);
assert(rc = 1);
close(fd);
io_destroy(ctx);
}
```
```
gcc -g -Og missing-syscall.c -o test-valgrind -laio
valgrind ./test-valgrind
```
output:
```
==39192== Memcheck, a memory error detector
==39192== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al.
==39192== Using Valgrind-3.22.0 and LibVEX; rerun with -h for copyright info
==39192== Command: ./test-valgrind
==39192==
--39192-- WARNING: unhandled amd64-linux syscall: 333
--39192-- You may be able to write your own handler.
--39192-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--39192-- Nevertheless we consider this a bug. Please report
--39192-- it at http://valgrind.org/support/bug_reports.html.
==39192==
==39192== HEAP SUMMARY:
==39192== in use at exit: 0 bytes in 0 blocks
==39192== total heap usage: 0 allocs, 0 frees, 0 bytes allocated
==39192==
==39192== All heap blocks were freed -- no leaks are possible
==39192==
==39192== For lists of detected and suppressed errors, rerun with: -s
==39192== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
```
--
You are receiving this mail because:
You are watching all bug changes.
