https://bugs.kde.org/show_bug.cgi?id=480052

            Bug ID: 480052
           Summary: WARNING: unhandled amd64-freebsd syscall: 580
    Classification: Developer tools
           Product: valgrind
           Version: 3.22 GIT
          Platform: FreeBSD Ports
                OS: FreeBSD
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: memcheck
          Assignee: jsew...@acm.org
          Reporter: asom...@gmail.com
  Target Milestone: ---

SUMMARY

memcheck does not handle the "fspacectl" syscall (syscall #580).


STEPS TO REPRODUCE
1.  Using FreeBSD 14/stable, 15.0-CURRENT, or 14.0-RELEASE with the tests
distribution installed:
2.  cd /usr/tests/sys/fs/fusefs
3. valgrind --tool=memcheck ./fallocate --gtest_filter=Fspacectl.ok -v

OBSERVED RESULT

==14536== Memcheck, a memory error detector
==14536== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al.
==14536== Using Valgrind-3.22.0.GIT and LibVEX; rerun with -h for copyright
info
==14536== Command: ./fallocate --gtest_filter=Fspacectl.ok -v
==14536== 
Note: Google Test filter = Fspacectl.ok
[==========] Running 1 test from 1 test suite.
[----------] Global test environment set-up.
[----------] 1 test from Fspacectl
[ RUN      ] Fspacectl.ok
INIT        ino= 0
ACCESS      ino= 1 mask=0x1
LOOKUP      ino= 1 some_file.txt
OPEN        ino=42 flags=0x2
--14536-- WARNING: unhandled amd64-freebsd syscall: 580
--14536-- You may be able to write your own handler.
--14536-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--14536-- Nevertheless we consider this a bug.  Please report
--14536-- it at http://valgrind.org/support/bug_reports.html.
/usr/home/somers/src/freebsd.org/src/tests/sys/fs/fusefs/fallocate.cc:335:
Failure
Expected equality of these values:
  0
  fspacectl(fd, 1, &rqsr, 0, &rmsr)
    Which is: -1

EXPECTED RESULT

The test should pass

SOFTWARE/OS VERSIONS
FreeBSD 14.0-RELEASE and later.

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to