Ross Lagerwall rosslagerw...@gmail.com added the comment:
I think this can be closed.
msync() is only called in mmap.flush() and it is checked for an error.
--
nosy: +rosslagerwall
___
Python tracker rep...@bugs.python.org
Brian Curtin cur...@acm.org added the comment:
That was changed in r84950 from #2643.
--
resolution: - out of date
stage: unit test needed - committed/rejected
status: open - closed
___
Python tracker rep...@bugs.python.org
Ralf Schmitt sch...@gmail.com added the comment:
No, I don't know how to provoke such an error other than passing illegal
parameters..(or munmap'ing the mmap'ed area).
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue2644
Brian Curtin cur...@acm.org added the comment:
Do you have a test case to reproduce the errors?
I see that we call msync followed by munmap, neither one checked.
--
nosy: +brian.curtin
stage: - test needed
___
Python tracker rep...@bugs.python.org
Changes by Brian Curtin cur...@acm.org:
--
priority: - normal
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue2644
___
___
Python-bugs-list mailing
New submission from Ralf Schmitt [EMAIL PROTECTED]:
mmapmodule.c's mmap_object_dealloc calls msync without checking for an
error.
--
messages: 65553
nosy: schmir
severity: normal
status: open
title: errors from msync ignored in mmap_object_dealloc
type: behavior
versions: Python 2.6
