This is the mail archive of the
cygwin-patches
mailing list for the Cygwin project.
Re: dlclose not calling destructors of static variables.
- From: Dave Korn <dave dot korn dot cygwin at googlemail dot com>
- To: cygwin-patches at cygwin dot com
- Date: Mon, 01 Feb 2010 22:36:38 +0000
- Subject: Re: dlclose not calling destructors of static variables.
- References: <4B62DDE6.5070106@gmail.com> <4B62F118.8010305@gmail.com> <20100129184514.GA9550@ednor.casa.cgf.cx> <4B66BF2F.4060802@gmail.com> <20100201162603.GB25374@ednor.casa.cgf.cx> <4B6710CE.40300@gmail.com> <20100201174611.GA26080@ednor.casa.cgf.cx> <20100201175123.GB26080@ednor.casa.cgf.cx> <4B672B74.4090808@gmail.com> <4B6736C1.8030101@gmail.com> <20100201215919.GA29662@ednor.casa.cgf.cx>
On 01/02/2010 21:59, Christopher Faylor wrote:
> Since the testcase (obviously?) worked for me it seems like this is pretty
> variable. I'd like to understand why the MEMORY_BASIC_INFORMATION method
> doesn't work before trying other things.
Hmm, well first off, looks like RegionSize is indeed relative to
BaseAddress, not AllocationBase after all:
http://msdn.microsoft.com/en-us/library/aa366775(VS.85).aspx
> RegionSize
>
> The size of the region beginning at the base address in which all pages
> have identical attributes, in bytes.
http://msdn.microsoft.com/en-us/library/aa366902(VS.85).aspx
> The function returns the attributes and the size of the region of pages
> with matching attributes, in bytes. For example, if there is a 40 megabyte
> (MB) region of free memory, and VirtualQuery is called on a page that is 10
> MB into the region, the function will obtain a state of MEM_FREE and a size
> of 30 MB.
cheers,
DaveK