Bug 369031 - WARNING: unhandled amd64-linux syscall: 308 (setns)
Summary: WARNING: unhandled amd64-linux syscall: 308 (setns)
Status: RESOLVED DUPLICATE of bug 343099
Alias: None
Product: valgrind
Classification: Developer tools
Component: general (show other bugs)
Version: 3.11.0
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Julian Seward
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-09-19 06:48 UTC by Marcin Juszkiewicz
Modified: 2018-11-21 03:08 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marcin Juszkiewicz 2016-09-19 06:48:03 UTC
<<<test_start>>>
tag=setns01_valgrind_memory_leak_check stime=1474195406
cmdline=" valgrind -q --leak-check=full --trace-children=yes setns01"
contacts=""
analysis=exit
<<<test_output>>>
--24584-- WARNING: unhandled amd64-linux syscall: 308
--24584-- You may be able to write your own handler.
--24584-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--24584-- Nevertheless we consider this a bug.  Please report
--24584-- it at http://valgrind.org/support/bug_reports.html.
setns01     1  TCONF  :  setns01.c:209: syscall(308) __NR_setns not supported on your arch
setns01     2  TCONF  :  setns01.c:209: Remaining cases not appropriate for configuration
<<<execution_status>>>
initiation_status="ok"
duration=1 termination_type=exited termination_id=32 corefile=no
cutime=60 cstime=2
<<<test_end>>>


Reproducible: Always
Comment 1 Marcin Juszkiewicz 2018-04-30 08:07:09 UTC
Can we close it? IIRC it was merged into valgrind.
Comment 2 Tom Hughes 2018-04-30 09:56:51 UTC
I see no sign that this has been added.
Comment 3 Brenda J. Butler 2018-11-21 03:08:38 UTC
This looks like a duplicate of 343099, and 343099 has a patch.

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