| Summary: | WARNING: unhandled arm64-linux syscall: 168 (getcpu) | ||
|---|---|---|---|
| Product: | [Developer tools] valgrind | Reporter: | bugger <subhayu.mustafi> |
| Component: | memcheck | Assignee: | Julian Seward <jseward> |
| Status: | RESOLVED UNMAINTAINED | ||
| Severity: | critical | CC: | tom |
| Priority: | NOR | ||
| Version First Reported In: | 3.11.0 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
bugger
2018-01-12 08:13:19 UTC
This system call was enabled a year ago - please update to the latest release. Thanks for your reply.. updated valgrind to 3.11.13 the latest release still it shows the same error... ==24489== Thread 2: ==24489== Syscall param epoll_ctl(event) points to uninitialised byte(s) ==24489== at 0x502F688: epoll_ctl (syscall-template.S:84) ==24489== by 0x48FA40F: grpc_init_epoll1_linux(bool) (in /usr/local/lib/libgrpc.so.5.0.0-dev) ==24489== Address 0x691b05c is on thread 2's stack ==24489== Uninitialised value was created by a stack allocation ==24489== at 0x48FA280: grpc_init_epoll1_linux(bool) (in /usr/local/lib/libgrpc.so.5.0.0-dev) No that's completely different - that's just valgrind doing it's job and telling you that your program is passing uninitialised data to a system call. |