Re: Consider exposing mmap_is_attached_or_noreserve

2019-02-28 Thread Corinna Vinschen
On Feb 28 12:50, E. Madison Bray wrote: > On Wed, Feb 27, 2019 at 5:17 PM Corinna Vinschen wrote: > > > > On Feb 27 16:38, E. Madison Bray wrote: > > > In order to handle such a case it might be nice if > > > mmap_is_attached_or_noreserve were able to be called by user code, > > > perhaps as a new

Re: Consider exposing mmap_is_attached_or_noreserve

2019-02-28 Thread E. Madison Bray
On Wed, Feb 27, 2019 at 5:17 PM Corinna Vinschen wrote: > > On Feb 27 16:38, E. Madison Bray wrote: > > Hello, > > > > A very technical request regarding Cygwin internals: In mmap.c there > > is a function mmap_is_attached_or_noreserve(void *addr, size_t len) > > which is called from Cygwin's excep

Re: Consider exposing mmap_is_attached_or_noreserve

2019-02-27 Thread Corinna Vinschen
On Feb 27 17:17, Corinna Vinschen wrote: > On Feb 27 16:38, E. Madison Bray wrote: > > Hello, > > > > A very technical request regarding Cygwin internals: In mmap.c there > > is a function mmap_is_attached_or_noreserve(void *addr, size_t len) > > which is called from Cygwin's exception handler in

Re: Consider exposing mmap_is_attached_or_noreserve

2019-02-27 Thread Corinna Vinschen
On Feb 27 16:38, E. Madison Bray wrote: > Hello, > > A very technical request regarding Cygwin internals: In mmap.c there > is a function mmap_is_attached_or_noreserve(void *addr, size_t len) > which is called from Cygwin's exception handler in the case of a > STATUS_ACCESS_VIOLATION. > > This is