Re: Assertion failed when trying to use ODBC in Windows 7 64 bit

[Dimiter 'malkia' Stanev <malkia@...>]

I guess my advice was bad, because retry probably ignored the assert, 
and something worse happened.

But the dump is good idea, but needs to be taken when the assert happens.

You can do that using ProcExp.

Download it from here: 
http://technet.microsoft.com/en-us/sysinternals/bb795533

Now once your application has stopped in that assert window (lua.exe 
that is), then follow the instructions below - e.g. find lua.exe (not 
System as it's shown in the picture below) and take a dump.

http://computersecuritystudent.com/FORENSICS/Proccess_Tools/lesson1/index.58.jpg

Full dump is preffered, but it might contain sensitive information 
(client information), then one can inspect it easier.

Mini dump would not have any memory dumps, so it's probably safer to 
start from there.

Once you have this, upload it, and someone can open the dump file.
I've opened the other dump file that you've sent to MS, but it crashes 
in odbc.dll.

On 3/8/2012 2:53 PM, Szabó, Ferenc wrote:
> Yes, it's Hungarian and means 'Retry'. :)
>
> I do not have Visual Studio.
> I pressed 'Retry' then lua.exe stopped and Win7 offered me to send bug
> report to MS.
> I have copied the 3 debug files (prepared by Win7) to my Dropbox:
> WERF0E0.tmp.mdmp - http://dl.dropbox.com/u/43546099/WERF0E0.tmp.mdmp
> WERF072.tmp.appcompat.txt -
> http://dl.dropbox.com/u/43546099/WERF072.tmp.appcompat.txt
> WERA9E0.tmp.WERInternalMetadata.xml -
> http://dl.dropbox.com/u/43546099/WERA9E0.tmp.WERInternalMetadata.xml
>
> Thanks for your help. :)
>
>
> 2012/3/8 Dimiter 'malkia' Stanev <malkia@gmail.com
> <mailto:malkia@gmail.com>>
>
>     It looks like you have a debugger.
>
>     Can you break in there. I can't read hungarian (if I'm not mistaken)
>     but I guess "Ismet" would mean Retry. Press that and it would get
>     you in the debugger.
>
>      >From there you should be able to see the value. Hopefully the
>     debug information is going to be enough.
>
>     Even if it's not. Then turn to disassembly, and go back in the stack
>     one two or three positions, you should see something comparing.
>
>     At least share the call stack with us, so we can guide you.
>     Ctrl+Alt+C is the default combination that brings the callstack in
>     Visual Studio (assuming that is what you have).
>
>
>     On 3/8/2012 1:45 PM, Szabó, Ferenc wrote:
>
>         @ Ignacio Burgueño:
>         SOCDOS is a simple char(3).
>         *
>
>         *
>         @ Dimiter 'malkia' Stanev:
>         I would do that. How could I print/log the actual code? I do not
>         know C.
>         Shall I need a C compiler?
>
>         Actually the driver is 32 bit driver of DataDirect Connect for
>         ODBC for
>         Oracle 8.1.6 (this version is not supported by Oracle for
>         Windows 7) and
>         I have no support for the DataDirect driver yet as the support
>         period is
>         already over. :(  (Pure me.)
>         So everything is identical except the OS that changed to 64 bit.
>         I can
>         use the ODBC with other programs (eg. MS Office) without problem.