Bug 264253 - Unhandled syscall: unix: 44 (profil)
Summary: Unhandled syscall: unix: 44 (profil)
Status: REPORTED
Alias: None
Product: valgrind
Classification: Developer tools
Component: memcheck (other bugs)
Version First Reported In: 3.10 SVN
Platform: macOS (DMG) macOS
: NOR normal
Target Milestone: ---
Assignee: Rhys Kidd
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-25 14:54 UTC by maelle.nodet
Modified: 2020-06-05 12:59 UTC (History)
4 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description maelle.nodet 2011-01-25 14:54:58 UTC
Version:           3.6.0
OS:                OS X

Hi,

I have the following problem:

----
WARNING: unhandled syscall: unix: 44
--64681-- You may be able to write your own handler.
--64681-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--64681-- Nevertheless we consider this a bug.  Please report
--64681-- it at http://valgrind.org/support/bug_reports.html.
----

So I report.
Thanks.


Reproducible: Didn't try
Comment 1 Clint Jeffery 2011-06-24 06:20:12 UTC
Bug also appeared in valgrind output reported to me by a user on Snow Leopard.
Comment 2 Alan S. Mazer 2012-05-24 00:59:20 UTC
I've got this too.  Not sure where it's coming from, and the procedure for addressing it (searching for unistd*.h) doesn't turn up anything useful on OS 10.6.4.
Comment 3 Rhys Kidd 2015-05-17 14:07:15 UTC
Alan, Clint or Maelle,
I'll take a look at fixing this. Would assist if there's a simple reproduction test case that you could provide to trigger this.
Comment 4 Rhys Kidd 2015-05-20 11:30:37 UTC
The syscall: unix: 44 is profil() which was deprecated some time around OS X 10.6 and fully removed in the xnu kernel shipped with OS X 10.7.

One of the last references: http://www.opensource.apple.com/source/xnu/xnu-1699.32.7/bsd/kern/syscalls.master
    profil(short *bufbase, size_t bufsize, u_long pcoffset, u_int pcscale); }

Given the syscall was deprecated < OS X 10.7, and the limited Mac Valgrind development resources at present, this unfortunately won't be a priority to resolve soon. I'll leave the bug open however and document the call in the V source code.
Comment 5 Paul Floyd 2020-06-05 12:59:28 UTC
I suspect that running a guest that is using profil() (or any such profiling API) would be of very limited use under Valgrind. Sensible uses cases to me are using profil() standalone or else profiling with callgrind/cachegrind.