RE: [Firebird-devel] ibeng32.dll

[Claudio V. C. <cv...@us...>]

> -----Original Message-----
> From: fir...@li...
> [mailto:fir...@li...]On Behalf Of Dmitri
> Zakharov
>
>   Recently I tried to use ibeng32.dll from FireBird 0.94
>   It was build via MS Visual C++ 6.0.
>   (it was renamed to gds32.dll of cource)
>   as a local data engine.
>   It seems the code contain some int 3 inside. (I am not sure...)

You should know that this "engine in a DLL" has not been used in years.
Don't know how successful it was when it was tested and why it was
abandoned, but certainly it's not in any official Borland binary
distribution.


>   Backup through isc_service behaves the same way (int 3),
>   Though backup file is created correctly.
>
>   Can anybody hint (advise) me a solution of this trouble?

I think that your option is to try to debug it. Have a small C program that
loads the DLL and makes the API calls (you can start from one of the API*.C
examples) and debug it with MSVC, until you jump inside the DLL and the
debugger asks for the source file(s).

C.