Bug 315936 - UNKNOWN task message [id 3403, to mach_task_self(), reply 0x2603] when running fork()ing tests on Mac OS X
Summary: UNKNOWN task message [id 3403, to mach_task_self(), reply 0x2603] when runnin...
Status: RESOLVED FIXED
Alias: None
Product: valgrind
Classification: Developer tools
Component: general (show other bugs)
Version: unspecified
Platform: Other macOS
: NOR normal
Target Milestone: ---
Assignee: Rhys Kidd
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-03-01 01:22 UTC by Peter Godman
Modified: 2015-06-13 03:05 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Godman 2013-03-01 01:22:21 UTC
#include <stdlib.h>
#include <unistd.h>

int main() {
    fork();
    exit(0);
}

$ valgrind --track-origins=yes --leak-check=full --read-var-info=no --quiet ./a.out
UNKNOWN task message [id 3403, to mach_task_self(), reply 0x2603]




Reproducible: Always

Steps to Reproduce:
1. Compile program above
2. Run with command line given above
3.Expected:  no errors 
Actual Results:  
Warning:  UNKNOWN task message [id 3403, to mach_task_self(), reply 0x2603]


Expected Results:  
No output
Comment 1 Julian Seward 2013-09-20 10:37:54 UTC
Noted.  Will require further 10.8 fixes.
Comment 2 Per Mildner 2014-01-15 13:12:48 UTC
I get a similar message in Mac OS X 10.7.5 from the above program:
UNKNOWN task message [id 3403, to mach_task_self(), reply 0x2503]
Comment 3 Rhys Kidd 2015-05-12 01:46:54 UTC
I believe this was fixed in r14952, which related to https://bugs.kde.org/show_bug.cgi?id=343523.

Can you confirm if this bug is still present in current Valgrind trunk? I can also check based on your regression test later this week.
Comment 4 Rhys Kidd 2015-05-12 13:15:27 UTC
Confirmed resolved with r14952.