Bug 369034 - WARNING: unhandled amd64-linux syscall: 136 (ustat)
Summary: WARNING: unhandled amd64-linux syscall: 136 (ustat)
Status: RESOLVED NOT A BUG
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:50 UTC by Marcin Juszkiewicz
Modified: 2021-10-04 18:02 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

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


Reproducible: Always
Comment 1 Marcin Juszkiewicz 2018-04-30 08:07:17 UTC 
Can we close it? IIRC it was merged into valgrind.
Comment 2 Tom Hughes 2018-04-30 09:56:18 UTC 
I see no sign that this has been added.
Comment 3 Mark Wielaard 2021-10-04 09:11:52 UTC 
This has been implemented for MIPS only. And I am not sure it is correct (for other arches).

NOTES
       ustat() is deprecated and has been  provided  only  for  compatibility.
       All new programs should use statfs(2) instead.
Comment 4 Marcin Juszkiewicz 2021-10-04 18:02:47 UTC 
As ustat() is deprecated there is no sense in keeping this bug open.