Mail Archives: cygwin/2002/06/19/09:43:25
> -----Original Message-----
> From: cygwin-owner AT cygwin DOT com [mailto:cygwin-owner AT cygwin DOT com]On Behalf
> Of Pavel Tsekov
> Sent: Tuesday, June 18, 2002 4:41 PM
> To: cygwin AT cygwin DOT com
> Subject: Re[2]: Rebase 1.5-1: Causes invalid page fault
>
>
> JT> On Tue, Jun 18, 2002 at 06:04:31PM +0200, Pavel Tsekov wrote:
> >> You printed just the first argument. There is a total of 11 arguments
> >> to this function.
> >>
> >> BOOL ReBaseImage(
> >> PSTR CurrentImageName,
[SNIP]
> >> ULONG_PTR *OldImageBase,
> JT> ^^^^
> JT> ****
> >> ULONG *NewImageSize,
> >> ULONG_PTR *NewImageBase,
> JT> ^^^^
> JT> ****
> >> ULONG TimeStamp
> >> );
>
> JT> The ULONG_PTR above is causing me some concern. Note that the above
> JT> signature does *not* agree with the header file (either MinGW or MSVC)
> JT> and I cannot find the definition of ULONG_PTR. Is the above a typo in
> JT> the MSDN or are OldImageBase and NewImageBase really suppose to be a
> JT> pointer to pointer?
>
> The above is from help library that is coming with the downloadable
> Platform SDK. It is dated November, 2001.
>
> I just grepped /usr/include/w32api:
>
> ./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"? I thought the concern was whether
--
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/
- Raw text -