Trouble after TOpenDialog.Execute

[Wargan]

Hello!
When using the TOpenDialog class, I'm having problems on the form. This happens like this:
Pressing the button will call the code:

Code: Pascal  [Select][+][-]

1. If OpenDialog1.Execute then
2. Begin
3.     ShowMessage (OpenDialog1.FileName);
4. End;

And nothing else.

The message is displayed, everything is working correctly, but when the main form is closed, the heaptc window appears: External error: SIGSEGV at address 7C919FCA. Interestingly, heaptc does not show memory leaks.

In the attachment, I attached a screenshot from the assembler window.

I thought that maybe it was a conflict between LCL and LazSolutions?

In my project there are the following dependencies:

• Virtualtreeview_package
• FCL
• SQLDBLaz
• Eccontrols
• LCL

On an empty form (New empty project) after calling TOpenDialog, there are no problems.

I ask you to help with the solution of this problem!

[Wargan]

p.s. after the removal of a piece of code above, no error occurs.

[balazsszekely]

Hi Wargan,

I did try to reproduce the issue with Lazrus Trunk/FPC 3.02 without success. So probably it was fixed since 1.6.4.

[Wargan]

I did try to reproduce the issue with Lazrus Trunk/FPC 3.02 without success. So probably it was fixed since 1.6.4.

Hmm... I have installed version 1.6.4))

Can someone explain to me what is the cause of the error in the RtlpWaitForCriticalSection method? I understand the SIGSEGV error occurs when the pointer is equal to nil, but ... what is the problem exactly THERE, I can not understand

[Wargan]

UPDATE: I played around with the build modes.
The error only appears in Debug mode, in Release mode it does not exist 

Judging by the documentation from MSDN, then probably a problem with the system libraries. In addition, I have Windows XP SP3 installed on my working netbook. Well, well ... I don't mind getting ideas from more experienced comrades ..)

[Martin_fr]

It is a bug in gdb. You can change some settings, in order to debug

http://wiki.lazarus.freepascal.org/GDB_Debugger_Tips#On_Windows_Open.2FSave.2FFile_or_System_Dialog_cause_gdb_to_crash

[Wargan]

Martin_fr, thank you very much! I'm glad if it helps others