Bug 369032 - WARNING: unhandled amd64-linux syscall: 205 (set_thread_area)
Summary: WARNING: unhandled amd64-linux syscall: 205 (set_thread_area)
Status: REPORTED
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: 2021-10-29 17:50 UTC (History)
3 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:48:50 UTC 
<<<test_start>>>
tag=set_thread_area01_valgrind_memory_leak_check stime=1474195515
cmdline=" valgrind -q --leak-check=full --trace-children=yes set_thread_area01"
contacts=""
analysis=exit
<<<test_output>>>
--24891-- WARNING: unhandled amd64-linux syscall: 205
--24891-- You may be able to write your own handler.
--24891-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--24891-- Nevertheless we consider this a bug.  Please report
--24891-- it at http://valgrind.org/support/bug_reports.html.
set_thread_area_01    1  TCONF  :  set_thread_area01.c:77: syscall(205) tests[i].syscall not supported on your arch
set_thread_area_01    2  TCONF  :  set_thread_area01.c:77: Remaining cases not appropriate for configuration
<<<execution_status>>>
initiation_status="ok"
duration=1 termination_type=exited termination_id=32 corefile=no
cutime=63 cstime=2
<<<test_end>>>


Reproducible: Always
Comment 1 Marcin Juszkiewicz 2018-04-30 08:07:12 UTC 
Can we close it? IIRC it was merged into valgrind.
Comment 2 Tom Hughes 2018-04-30 09:56:40 UTC 
I see no sign that this has been added.
Comment 3 Mark Wielaard 2021-10-04 09:17:02 UTC 
This has only been implemented for x86 (32bits)