Bug 351632 - UNKNOWN fcntl 97 on OS X 10.11
Summary: UNKNOWN fcntl 97 on OS X 10.11
Status: RESOLVED FIXED
Alias: None
Product: valgrind
Classification: Developer tools
Component: memcheck (show other bugs)
Version: 3.10 SVN
Platform: macOS (DMG) macOS
: NOR normal
Target Milestone: ---
Assignee: Rhys Kidd
URL:
Keywords:
Depends on:
Blocks: 348909
  Show dependency treegraph
 
Reported: 2015-08-23 03:06 UTC by Rhys Kidd
Modified: 2023-12-29 09:12 UTC (History)
3 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Rhys Kidd 2015-08-23 03:06:44 UTC
Introduced between DP5 & DP7 of OS X 10.11 (El Capitan), this error message is prevalent across c.350 regression tests.

  UNKNOWN fcntl 97!
  UNKNOWN fcntl 97! (repeated 2 times)
  UNKNOWN fcntl 97! (repeated 4 times)
  etc

Reproducible: Always

Steps to Reproduce:
1. perl tests/vg_regtest memcheck/tests/addressable

Actual Results:  
In diff file:

  UNKNOWN fcntl 97!
Comment 1 Rhys Kidd 2015-09-03 13:07:05 UTC
Warning silenced on r15619.
Awaits xnu source code release to resolve properly.
Comment 2 captainabernathy 2015-10-28 06:48:03 UTC
I recently switched to El Capitan and started getting this error. However, I was able to find a odd, albeit, not exactly technical fix for it based around some other bugs I worked out with El Capitan. 

Apparently, during the upgrade to El Capitan, the OS randomly decides whether or not to keep custom configuration files as well as additional extensions or modules that you may have added to its baseline software. 

For me, my Apache and php configuration files were reset, and some extensions that I had added were gone altogether. Anyway, when I started to get the UNKNOWN fcntl 97! error from Valgrind, I began to suspect that maybe something that its configuration depended on had been wiped from the OS during the upgrade.

So, I delete Valgrind, and attempted to rebuild it, but my attempts failed bc, as it turns out, the El Capitan upgrade had removed XCode Command Line Tools from my system. After reinstalling XCode Command Line Tools, I was able to successfully rebuild Valgrind, and upon testing the new installation, I no longer receive UNKNOWN fcntl 97! error.
Comment 3 Rhys Kidd 2015-10-31 00:19:00 UTC
Hello captainabernathy,

That would be because, in the process of rebuilding Valgrind, you upgraded beyond r15619. I've silenced the warning for now, until Apple release the xnu kernel source code (which typically has taken a month or so).
Comment 4 Julian Seward 2016-07-04 14:14:55 UTC
Rhys, what is the status of this now?  Can it be resolved more fully, per comment 1 ?
Comment 5 Rhys Kidd 2016-07-09 00:42:22 UTC
Hello Julian,
All information on the interface is now available. I hope to get some time to implement it in Valgrind in the next few weeks.
Comment 6 Paul Floyd 2023-12-29 09:12:25 UTC
On macOS 10.13 I get

perl tests/vg_regtest memcheck/tests/addressable
addressable:     valgrind   ./addressable 

== 1 test, 0 stderr failures, 0 stdout failures, 0 stderrB failures, 0 stdoutB failures, 0 post failures ==

LGTM.