lazarus 0.9.22 window build problems with debugger
lazarus / 12-Debugger

----------------------------------------------------------------------
mikaelo · 2007-03-29 13:45

Just downloaded the last version for windows and installed it.
When apps (even tried the empty default empty form project) are run
from inside the IDE, they will segfault. The generated executable ran
fine outside of the IDE.

So now I'm have to go back to 0.9.20 to be able to use debugger.

Mikael

----------------------------------------------------------------------
mikaelo · 2007-03-29 14:23

Problem seem to be my windows XP development box. It don't seem to be
compatible with lazarus as neither 0.9.20 nor 0.9.22 works on it.
Maybe I'll try is again an a few months to see if it's mature enough
to be able to debug on windows.

Guess i'll just have to continue with delphi 7 on the windows side.

Thanks for a good effort.

----------------------------------------------------------------------
Vincent Snijders · 2007-03-29 14:29

That is strange, because I use and develop lazarus on windows XP SP2
and dont'have such problems.

Where do they segfault? What happens when you continue?

----------------------------------------------------------------------
Marc · 2007-03-30 07:55

Do you have a manifest for your app ?
It is a known issue that the debugger might crash is a manifest is
used.

----------------------------------------------------------------------
Vincent Snijders · 2007-03-30 07:59

But this doesn't happen always. Lazarus.exe has a manifest too, and I
can debug that in Lazarus too.

----------------------------------------------------------------------
pyrasoftware · 2007-05-12 23:55

Hopefully you might find the following useful, it is a workaround for
the problem I've had with debugging within windows (and sound similar
to the issue you have had)...

------------
Dialog Displayed - Error
Project  raised exception class 'External: SIGSEGV'
------------
Click 'OK'
------------
Dialog Displayed - Execution Paused

Adress: $7C918FEA
Procedure ntdll!RTLPWaitForCriticalSection
File:

(Some day an assembler window might popup here
------------
Click 'OK'
------------
Generate or remove a breakpoint - doesn't matter where (have tried in
both a unit or the lpr file)  I tend to use the lpr file but either
seem to work fine.
------------
Dialog Displayed - Execution Paused

Adress: $7C901231
Procedure ntdll!DbgUiConnectToDbg
File:

(Some day an assembler window might popup here
------------
Click 'OK'
------------
Unpause the application (toolbar or menu seems to work fine).
------------
It seems to work fine (for me at least) after this - debugging working
as expected (though the project window does sometimes appear behind
the form).

Kind Regards,
Steven Coombs