Mail Archives: cygwin/2002/06/18/19:21:07
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,
>> PSTR SymbolPath,
>> BOOL fReBase,
>> BOOL fRebaseSysfileOk,
>> BOOL fGoingDown,
>> ULONG CheckImageSize,
>> ULONG *OldImageSize,
>> 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 :)
--
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 -