Bug 461926 - Receive "unhandled amd64-linux syscall: 434" in Gtk program
Summary: Receive "unhandled amd64-linux syscall: 434" in Gtk program
Status: RESOLVED DUPLICATE of bug 464609
Alias: None
Product: valgrind
Classification: Developer tools
Component: general (other bugs)
Version First Reported In: 3.19.0
Platform: Debian unstable Linux
: NOR normal
Target Milestone: ---
Assignee: Julian Seward
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-11-16 23:06 UTC by rastersoft
Modified: 2023-04-19 23:33 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description rastersoft 2022-11-16 23:06:39 UTC
SUMMARY

When running a Gtk program and clicking on a button, I receive the message: "unhandled amd64-linux syscall: 434", and "Warning: noted but unhandled ioctl 0x5441 with no size/direction hints."

STEPS TO REPRODUCE

1. Download "tiled_widget" ( https://gitlab.com/rastersoft/tiled-widget ) and build the example (just type "make")
2. Run it with "valgrind ./test_terminal"
3. Split the tiles using the buttons with the vertical ("|") and horizontal ("-") bars, or close them with the "X" buttons. 

OBSERVED RESULT

Every time one of the "split" buttons is pressed, the above message appears in Valgrind.

EXPECTED RESULT

Valgrind should recognize all the syscalls and IOCTLs.

SOFTWARE/OS VERSIONS
Debian Unstable with Gnome Shell 43.

ADDITIONAL INFORMATION
Comment 1 Paul Floyd 2022-11-17 08:33:50 UTC
I recently pushed a change that should stop the "no size/direction" message. For that you'll either have to build your own Valgrind, hope that your package maintainer merges that change or wait for 3.21 to be packaged.

According to https://github.com/torvalds/linux/blob/master/arch/x86/entry/syscalls/syscall_64.tbl

syscall 434 is

434	common	pidfd_open		sys_pidfd_open

I need to check what this syscall does,
Comment 2 Mark Wielaard 2023-04-19 23:33:55 UTC

*** This bug has been marked as a duplicate of bug 464609 ***