[SOLVED] Process Exit: 0331
lazarus / 21-General

----------------------------------------------------------------------
Dodo1977 · 2021-12-27 08:23

Up until now I've always managed to find my answer with the search
function, but alas, the day that I feared for so long has finally
arrived. I'm stuck.

For some unknown reason the programme I've been working on, off and on
for the past few years, has stopped working. It compiles fine. When I
run it the Lazarus titlebar says "debugging" for a few seconds, and
then nothing.

I added a breakpoint on the first row of code in the .lpr file, but it
doesn't fire!

Code: Pascal  [Select][+][-]window.onload = function(){var x1 =
document.getElementById("main_content_section"); if (x1) { var x =
document.getElementsByClassName("geshi");for (var i = 0; i begin 
RequireDerivedFormResource := True;  Application.Initialize; 
Application.CreateForm(TMainForm, MainForm);  Application.Run;end. 
I also upgraded to the newest version of Lazarus (2.0.12 with FPC
3.2.0), but that didn't change anything.

Eventually I found the Event viewer (log attached) and that gives me a
"Process Exit: 0331", but I can find only 1 post on that error and
that's about a custom written DLL. I'm not using any custom DLL,
outside maybe a few for Firebird SQL.

I'm at a loss, how can I debug this error without any info about when
and where it is triggered?

----------------------------------------------------------------------
zoltanleo · 2021-12-27 08:35

Hi Dodo1977

What debug mode are you using?

----------------------------------------------------------------------
Dodo1977 · 2021-12-27 08:42

Not sure, the standard mode I suppose.

----------------------------------------------------------------------
Dodo1977 · 2021-12-28 10:13

Nevermind, I found the problem.

In the event viewer I noticed several Firebird-related DLL's were
loaded. When I removed them, and thus they weren't loaded anymore, my
application generated an error in connecting to the database. I
commented out that code and then it started. So the problem was
isolated to Firebird. I upgraded all components to the latest version
( 3.0.8 ), but to no avail.
Then I remembered my application runs a stored procedure directly
after connecting to the database. It turned out this sp generated an
error. After resolving that everything was back to normal.
Alas, 4 hours well spent