On 29 May 2006 14:04, Dave Korn wrote:
> I really can't understand why it won't let us allocate the memory.
<lightbulb> Yes I can!
> Here's the surrounding area info from !vadump:
>
> BaseAddress: 00230000
> AllocationBase: 00230000
> AllocationProtect: 00000002 PAGE_READONLY
> RegionSize: 00003000
> State: 00001000 MEM_COMMIT
> Protect: 00000002 PAGE_READONLY
> Type: 00040000 MEM_MAPPED
>
> BaseAddress: 00233000
> AllocationBase: 00000000
> RegionSize: 0000d000
> State: 00010000 MEM_FREE
> Protect: 00000001 PAGE_NOACCESS
> BaseAddress: 00240000
> AllocationBase: 00240000
> AllocationProtect: 00000004 PAGE_READWRITE
> RegionSize: 00013000
> State: 00001000 MEM_COMMIT
> Protect: 00000004 PAGE_READWRITE
> Type: 00020000 MEM_PRIVATE
>
> So AFAICT the memory is free and should be allocatable, but it really
> isn't going to let us:
Because the thing before it is a memory mapped file, and so it has a 64kB
granularity, and *that's* why we can't allocate the tail-end of the 0x23....
page. Hah! That's also why trying to forcibly .vmfree it didn't work!
Um, as to what to do about it, that's another matter... haven't figured out
*what* it is yet. But I have figured out that it has the same committed size
as \BaseNamedObjects\cygwin1S4.mtinfo.2 - 0x3000 - and none of the other
shared section objects are that size. Watson, I believe we have a suspect!
cheers,
DaveK
--
Can't think of a witty .sigline today....
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
