Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com From: "Bernard A Badger" To: Subject: RE: Re[2]: Rebase 1.5-1: Causes invalid page fault Date: Wed, 19 Jun 2002 10:51:30 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal Importance: Normal In-Reply-To: <200206191406.g5JE6uGN026534@adams0-57.reshall.ou.edu> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 > -----Original Message----- > > > ./basetsd.h:100:typedef unsigned long ULONG_PTR, *PULONG_PTR; > > > So it is not a pointer to pointer. They have chosen a strange name > > > though :) > > > Which "it" are you talking about? The typedef you found defines > > ULONG_PTR as a pointer to unsigned long, and also defines PULONG_PTR > > as a pointer to pointer to unsigned long. But I thought the issue > > was the type of NewImageBase. > > No, `typedef unsigned long ULONG_PTR' defines `ULONG_PTR' as a synonym > for `unsigned long'. > > Btw., if I remember the MSDN documentation correctly, ULONG_PTR is > supposed an integer with the the same /size/ as a pointer, but also a > typedef for unsigned long where possible. Hence the name. > > > The question was whether > > ULONG_PTR *NewImageBase, > > defined a pointer to a pointer --- it does! *NewImageBase defines > > NewImageBase as a pointer to ULONG_PTR, which is itself a pointer, > > so it is, again, a pointer-to-pointer-to-unsigned-long. > > No, it's a pointer to unsigned long which is really a pointer. > > Jon Cast Ack! You are so right! I was blinded by the "_PTR" in the name ULONG_PTR, and didn't understand that that was the "strange name" you meant. My apologies to all. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/