I have no idea. I have no idea what you're doing or how you're doing it, what
platform you're doing it on or what tools you're doing it with. However, I do
know that if you have a LocalID with a value of, say 0x01020304, then in the
.pdb file, it should appear as 01 02 03 04 if you do a hex dump.
-- Keith
Sergio Carvalho <[EMAIL PROTECTED]> on 09/24/99 01:28:47 AM
Please respond to [EMAIL PROTECTED]
Sent by: Sergio Carvalho <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc: (Keith Rollin/HQ/3Com)
Subject: Re: Endian problems
Could it be that the LocalID is in fact a pair of Words, not a DWord as
indicated in the DataPrv header?
[EMAIL PROTECTED] wrote:
> In general,
>
> 01 02 03 04
>
> should be converted to:
>
> 04 03 02 01
>
> I'm not sure what problems you're experiencing with the LocalID.
>
>
> -- Keith Rollin
>
> Sergio Carvalho <[EMAIL PROTECTED]> on 09/24/99 01:00:41 AM
>
> Please respond to [EMAIL PROTECTED]
>
> Sent by: Sergio Carvalho <[EMAIL PROTECTED]>
>
> To: [EMAIL PROTECTED]
> cc: (Keith Rollin/HQ/3Com)
> Subject: Endian problems
>
> How should double words be swapped, when converting from little-endian
> to big-endian? A DWord:
> 01 02 03 04
> should become:
> 04 03 02 01
> or should it become:
> 02 01 04 03
>
> I expected it to be the first case. But when building a pdb, I had to
> use the second case to convert the record localID. the LocalID type is
> typedefed onto a DWord on the DataMgrPrv.h header. To confuse me more,
> the creatorID and database type fall onto the first case. A DB type of
> 'data' must be swapped to 'atad'...
>
> I feel lost.
>
> --
> Sergio Carvalho
> ---------------
> [EMAIL PROTECTED]
>
> If at first you don't succeed, skydiving is not for you
--
Sergio Carvalho
---------------
[EMAIL PROTECTED]
If at first you don't succeed, skydiving is not for you
