Re: new error message from Valgrind
Tom Hughes via Valgrind-users <[email protected]>
| Newsgroups | gmane.comp.debugging.valgrind |
|---|---|
| Message-ID | <[email protected]> |
On 28/07/2022 21:39, Mark Roberts wrote: > I recently upgraded from Ubutu 20.04 to 22.04 and am now getting a new > error message from Valgrind: > > --915-- WARNING: unhandled amd64-linux syscall: 334 > > --915-- You may be able to write your own handler. > > --915-- Read the file README_MISSING_SYSCALL_OR_IOCTL. > > --915-- Nevertheless we consider this a bug. Please report > > --915-- it at http://valgrind.org/support/bug_reports.html > <http://valgrind.org/support/bug_reports.html>. > > Using same version of Valgrind as before (3.17). > > Any ideas as to what’s happening? Yes, your libc has started trying to use rseq. It's harmless - the next version of valgrind will silently reject it with ENOSYS which is what is happening now anyway just with a warning. Tom -- Tom Hughes ([email protected]) http://compton.nu/ _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users