Bug 447386 - Unhandled syscall on PPC32
Summary: Unhandled syscall on PPC32
Status: RESOLVED DUPLICATE of bug 416753
Alias: None
Product: valgrind
Classification: Developer tools
Component: memcheck (show other bugs)
Version: 3.15 SVN
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Julian Seward
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-12-22 13:47 UTC by derplip
Modified: 2022-01-26 15:15 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description derplip 2021-12-22 13:47:44 UTC
When I run my application with Valgrind on a 32 Bit PowerPC  platform I get lots of these messages:

WARNING: unhandled ppc32-linux syscall: 407

The related name can be found in unistd_32.h:
#define __NR_clock_nanosleep_time64     407

Do I understand correctly that I have to write the appropriate handler myself?
Comment 1 Mark Wielaard 2021-12-22 14:14:28 UTC
Just upgrade to valgrind 3.16.0 or later (latest is 3.18.1) 3.15.0 is really old.

*** This bug has been marked as a duplicate of bug 416753 ***
Comment 2 derplip 2021-12-22 18:22:15 UTC
Ok thanks!
Comment 3 derplip 2022-01-24 16:03:04 UTC
I was not able to install 3.18 because of a Yocto/poky incompatibility, so I chose 3.17. 
There is still one message: WARNING: unhandled ppc32-linux syscall: 325

Do you know if this is fixed in 3.18?
Comment 4 Mark Wielaard 2022-01-26 15:15:29 UTC
(In reply to derplip from comment #3)
> I was not able to install 3.18 because of a Yocto/poky incompatibility, so I
> chose 3.17. 
> There is still one message: WARNING: unhandled ppc32-linux syscall: 325
> 
> Do you know if this is fixed in 3.18?

syscall 325 on ppc32 is prlimit64.
This doesn't seem to be hooked up on ppc32 (but is for ppc64).

Please don't just reopen old bugs for unrelated issues.
And please always test against the latest release of a git trunk build.

Feel free to open a new bug report to get ppc32 prlimite64 (syscall nr 325) hooked up.

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