On Jul 14 09:42, Brian Ford wrote:
> On Fri, 14 Jul 2006, Corinna Vinschen wrote:
> > I'm not sure we really want to do that, certainly not for 1.5.21. If
> > you need this sort of functionality, switch off MAP_NORESERVE.
>
> Sure, I know how to work around it.
>
> I just wanted to point out tha
On Fri, 14 Jul 2006, Corinna Vinschen wrote:
> Unfortunately the OS functions don't trigger the exception handler of
> the application, so the standard way of doing this doesn't work here.
That's what I figured.
> There's no way around that except for wrapping each and every call to an
> OS funct
On Jul 13 13:52, Brian Ford wrote:
> > On Thu, 13 Jul 2006, Corinna Vinschen wrote:
> > > I added an (hopefully) appropriate patch, which commits a page within a
> > > MAP_NORESERVE area when memory in this page is accessed by the
> > > application. If commiting the memory fails, SIGBUS is generat
On Thu, 13 Jul 2006, Brian Ford wrote:
> On Thu, 13 Jul 2006, Corinna Vinschen wrote:
> > I added an (hopefully) appropriate patch, which commits a page within a
> > MAP_NORESERVE area when memory in this page is accessed by the
> > application. If commiting the memory fails, SIGBUS is generated.
On Jul 13 10:07, Brian Ford wrote:
> On Thu, 13 Jul 2006, Corinna Vinschen wrote:
> > Shared anonymous maps seem to be possible (and would probably make sense
> > to minimze the swap space footprint), but are somewhat tricky since it's
> > not quite clear what happens to memory which is commited in
On Thu, 13 Jul 2006, Corinna Vinschen wrote:
> I just read the Linux man page (again), and I seem to have missed some
> important bits. The above semantics are not implemented this way in
> Cygwin. A private anonymous mmap is actually just an area allocated
> with VirtualAlloc. A MAP_NORESERVE
On Jul 12 15:57, Brian Ford wrote:
> On Wed, 12 Jul 2006, Corinna Vinschen wrote:
>
> > The problem results from introducing MAP_NORESERVE in 1.5.19. That's
> > the reason the same code works on 1.5.18. Your code simply defines
> > MAP_NORESERVE to 0 under 1.5.18.
>
> While that is true, I comp
On Wed, 12 Jul 2006, Corinna Vinschen wrote:
> The problem results from introducing MAP_NORESERVE in 1.5.19. That's
> the reason the same code works on 1.5.18. Your code simply defines
> MAP_NORESERVE to 0 under 1.5.18.
While that is true, I compiled the STC with MAP_NORESERVE defined under
the
On Jul 12 13:43, Brian Ford wrote:
> On Wed, 12 Jul 2006, Corinna Vinschen wrote:
> > On Jul 12 10:48, Brian Ford wrote:
> > > This is just a heads up for now as I plan to try and produce an STC
> > > with cygcheck output later today or tomorrow as time allows. But, just in
> > > case it rings any
On Wed, 12 Jul 2006, Corinna Vinschen wrote:
> On Jul 12 10:48, Brian Ford wrote:
> > This is just a heads up for now as I plan to try and produce an STC
> > with cygcheck output later today or tomorrow as time allows. But, just in
> > case it rings any bells...
>
> Does it work with 1.5.20?
No,
On Jul 12 10:48, Brian Ford wrote:
> This is just a heads up for now as I plan to try and produce an STC
> with cygcheck output later today or tomorrow as time allows. But, just in
> case it rings any bells...
Does it work with 1.5.20?
*corinna mumbles something about a reproducible, self-contai
11 matches
Mail list logo
