Bug 205788

Summary:	mmap(0x0, 688128) failed in UME with error 13 (Permission denied)
Product:	[Developer tools] valgrind	Reporter:	Angus <AngusCMarch>
Component:	memcheck	Assignee:	Julian Seward <jseward>
Status:	RESOLVED FIXED
Severity:	normal	CC:	mnemo, tom
Priority:	NOR
Version First Reported In:	3.3.1
Target Milestone:	wanted3.5.1
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Angus 2009-08-31 15:04:47 UTC

The error in the summary was sent to the stderr. In the valgrind log file I got this:
--2305-- WARNING: unhandled syscall: 275
--2305-- You may be able to write your own handler.
--2305-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--2305-- Nevertheless we consider this a bug.  Please report
--2305-- it at http://valgrind.org/support/bug_reports.html.

The program continues and I haven't been able to detect any further problems yet. This has happened on more than 1 occasion with this binary.

Comment 1 Tom Hughes 2009-10-27 16:15:46 UTC

Well the first thing to say is that the two issues are entirely unrelated.

The second thing is that you're using a pretty ancient version, so is either problem happening in more recent versions?

The third thing is that you haven't said what architecture you are using, so it isn't possible to work out what that system call is. I'm guessing it's 32 bit x86 though? In which case that is the get_mempolicy system call and it is implemented in the current codebase.

Comment 2 Angus 2009-10-28 01:17:18 UTC

Actually, I was running on an AMD64. From what I've learned in the months since, 275 seems to be the splice() system call. I have no idea what the mmap() problem was all about, but I'm afraid I don't even remember what project this was working on.

Comment 3 Tom Hughes 2010-02-23 11:51:35 UTC

Support for the splice system call has been committed as r11055.

If the mmap error happens again in a recent version then please raise a new bug for that.

Comment 4 Tom Hughes 2010-03-11 23:29:28 UTC

*** Bug 230377 has been marked as a duplicate of this bug. ***

Comment 5 Martin Olsson 2010-03-12 21:30:43 UTC

@Tom Hughes, is it safe to take the r11055 commit and apply/backport it to the valgrind in Ubuntu Lucid (valgrind-3.6.0.SVN-Debian)?