On 18/08/10 01:51, Marcus Meissner wrote:
On Wed, Aug 18, 2010 at 01:00:35AM +1000, Peter Urbanec wrote:
I'm seeing crashes in FindNextFileW/FindNextFileA due to what
looks like a 64 bit HANDLE value being truncated to 32 bits.
Check if your code uses "int" in its FindNextFile or findfirst thi
the assertion `addr->Mode == AddrModeFlat' failed is likely an address
returned by dbghelp which is not properly initialized.
Could you send me off line the .exe (and associated DLL if any) so that I
can check it
TIA
2010/8/17 Peter Urbanec
>
> Hi,
>
> I'm trying to get a fairly complex Win64 a
On Tue, Aug 17, 2010 at 05:51:55PM +0200, Marcus Meissner wrote:
>
> The Wine code is correct as-is, but perhaps the Windows win64 code generates
> only handles with 32bit.
That it very likely.
There are windows #defines/inline functions that convert HANDLE <=> long.
Remember there are some funct
On Wed, Aug 18, 2010 at 01:00:35AM +1000, Peter Urbanec wrote:
> Hi,
>
> I'm trying to get a fairly complex Win64 application to work with
> wine. I'm seeing crashes in FindNextFileW/FindNextFileA due to what
> looks like a 64 bit HANDLE value being truncated to 32 bits. I
> thought that I would
Hi,
I'm trying to get a fairly complex Win64 application to work with wine.
I'm seeing crashes in FindNextFileW/FindNextFileA due to what looks like
a 64 bit HANDLE value being truncated to 32 bits. I thought that I would
employ winedbg to help me, but I can't get very far. I don't have any
