Zeoslib Portal

Hail,

Compile Error, Lazarus (Lazarus-0.9.27-17562-fpc-2.2.2-20081124-win32) with Zeos (Oracle xe).
This creates the message below
"The gdb.exe encountered a problem and needs to close."
I do not know if it is problem with Lazarus Zeos.Fiz or with a test using zeos postgresql was normal with the problem is only with Oracle.


Debugger Error
Oops, the debugger entered the error state
Save your work now!

Hi Stop, and hope the best, we're pulling the plug

Something strange yet, to compile this by giving conflicting with Delphi 2007 and D2009, which I installed on my machine.

Hi elidorio2,

I only can say that ZeosLib 6.6.4 and also applications using ZeosLib 6.6.4 compile with no problems unter the official Lazarus 0.9.26 Release.

Could you please try to compile under 0.9.26 since 0.9.27-17562 is just a snapshot of Lazarus and not an official release.

This is not a compiler error, but a debugger problem. So the problem occurs at runtime. Does your compiled exe work outside lazarus?

Mark

Hello
So I tried with Zeos 6.6.4 and 0.9.26 with Lazarus. Encounter the same problem. The error occurs only with Oracle, with Firebird was normal.
This mistake happens at the time of compilation.
Already tested in several machines and is the same thing. I am compiling Lazarus with this program.

--
Edson

This mistake happens at the time of compilation.

I still believe you confuse 'compilation' with 'compile+debug'. If there's a compiler error you should get it in the messages frame and gdb.exe doesn't even start (and thus can't fail).
In your case I'm sure an exe file has been created and compilation is done.

Unfortunately, because compiler errors are easier to find. Now the big question is 'why/where does the debugger fail exactly.
Are you setting connection.connected := true at design time or at runtime?
Try setting it in the OnFormCreate and add a debug point. If it stops on that point without failing and fails beforethe next line of code has passed, this might give us a hint.

Mark

Problem / Solution

We did several tests and noticed that the problem occurs only when using RUN or F9 of Lazarus. When compiled with CTRL + F9, the application compiles normally.