Bug 423095 - Unhandled syscall 315
Summary: Unhandled syscall 315
Status: RESOLVED DUPLICATE of bug 369029
Alias: None
Product: valgrind
Classification: Developer tools
Component: memcheck (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Julian Seward
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-06-17 09:47 UTC by fanx07
Modified: 2020-06-17 18:38 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
glib C file to reproduce this (217 bytes, text/x-csrc)
2020-06-17 09:47 UTC, fanx07
Details

Note You need to log in before you can comment on or make changes to this bug.
Description fanx07 2020-06-17 09:47:23 UTC
Created attachment 129442 [details]
glib C file to reproduce this

SUMMARY

--17129-- WARNING: unhandled amd64-linux syscall: 315
==17129==    at 0xAF70839: syscall (syscall.S:38)
==17129==    by 0x5277261: g_system_thread_get_scheduler_settings (gthread-posix.c:1187)
==17129==    by 0x5255913: g_thread_pool_new (gthreadpool.c:608)
==17129==    by 0x12E09C: redis_restore (redis.c:1759)
==17129==    by 0x119E73: create_everything (main.c:861)
==17129==    by 0x119E73: main (main.c:885)
--17129-- You may be able to write your own handler.
--17129-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--17129-- Nevertheless we consider this a bug.  Please report
--17129-- it at http://valgrind.org/support/bug_reports.html.


STEPS TO REPRODUCE
1. Compile and run attached C program under valgrind


OBSERVED RESULT
Unhandled syscall

EXPECTED RESULT
No Unhandled syscall error

SOFTWARE/OS VERSIONS
Ubuntu 18.04.4 LTS \n \l
Valgrind 3.16.0

ADDITIONAL INFORMATION
-
Comment 1 Mark Wielaard 2020-06-17 18:38:58 UTC

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