X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Sat, 6 Jun 2009 10:49:24 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: ASLR sometimes stops working on Vista with 1.7? [was: Re: 	Cygwin     1.7  release (was ...)]
Message-ID: <20090606084924.GI23519@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <1244131746 DOT 30024 DOT 1318796263 AT webmail DOT messagingengine DOT com> <4A282063 DOT 9030804 AT users DOT sourceforge DOT net> <4A286B99 DOT 6020702 AT users DOT sourceforge DOT net> <20090605120936 DOT GD23519 AT calimero DOT vinschen DOT de> <4A293237 DOT 2010102 AT cwilson DOT fastmail DOT fm> <20090605163510 DOT GF23519 AT calimero DOT vinschen DOT de> <4A296778 DOT 2080507 AT cwilson DOT fastmail DOT fm> <20090605213012 DOT GG23519 AT calimero DOT vinschen DOT de> <4A29B510 DOT 3020601 AT gmail DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4A29B510.3020601@gmail.com>
User-Agent: Mutt/1.5.19 (2009-02-20)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On Jun  6 01:15, Dave Korn wrote:
> Corinna Vinschen wrote:
> 
> > Not good.  I'm puzzled where this allocated 68K region is exactly coming
> > from, but it really looks like something which occurs in or near dlopen.
> > 
> > I'm going to debug this further tomorrow.  I guess that goes without
> > saying, but I'd be glad for any help.
> 
>   I'll just suggest that these problems can often be debugged more easily in
> windbg than gdb, what with gflags/appverifier heap tracking, !vad, !heap, and
> related commands.  The gflags FLG_HEAP_ENABLE_TAG_BY_DLL might come in handy here.

Right.  You might have noticed in my mail that I refer to WinDbg
already.  It has a couple of invaluable helpers.  !vprot is one of my
favorites, as well as the many available display formats in the memory
window.

This morning I woke up and suddenly knew what's going on.  It's the size
of a structure, which had a size of 320 bytes before.  Now it has a size
of 65596 bytes since the filename stored in it is now a potentially 32K
long wide character string.  The structure must be shrinked again.  I
guess I have a patch by tonight.


Stay tuned,
Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
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/