Bug 378892 - Unhandled amd64-linux syscall: 324 [membarrier]
Summary: Unhandled amd64-linux syscall: 324 [membarrier]
Status: RESOLVED FIXED
Alias: None
Product: valgrind
Classification: Developer tools
Component: memcheck (other bugs)
Version First Reported In: 3.12.0
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Julian Seward
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-04-17 19:32 UTC by Phil
Modified: 2019-05-31 13:13 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Phil 2017-04-17 19:32:34 UTC 
The following appears immediately upon execution:

phil@phil:~/tmp/Bridge$ valgrind --leak-check=yes ./Bridge
==23243== Memcheck, a memory error detector
==23243== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==23243== Using Valgrind-3.12.0 and LibVEX; rerun with -h for copyright info
==23243== Command: ./Bridge
==23243== 
--23243-- WARNING: unhandled amd64-linux syscall: 324
--23243-- You may be able to write your own handler.
--23243-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--23243-- Nevertheless we consider this a bug.  Please report
--23243-- it at http://valgrind.org/support/bug_reports.html.
Comment 1 Tom Hughes 2017-04-17 20:03:44 UTC 
This appears to be membarrier and should be fairly simple to support.
Comment 2 Mark Wielaard 2019-05-31 13:13:31 UTC 
commit 959a54cb3a631bb61420f1784a0c8585af24349e
Author: Bart Van Assche <bart.vanassche@wdc.com>
Date:   Fri Jun 15 08:24:53 2018 -0700

    Add support for the Linux membarrier() system call
    
    Signed-off-by: Bart Van Assche <bart.vanassche@wdc.com>