Vojtěch Čihák via Lazarus
2018-07-13 14:01:51 UTC
Hi,
when I write following code (to force SIGSEGV)
Â
unit Unit1;
{$mode objfpc}{$H+}
Â
interface
Â
uses
 Classes, SysUtils, Forms, Controls, Graphics, Dialogs, StdCtrls;
Â
type
 { TForm1 }
 TForm1 = class(TForm)
  Button1: TButton;
  procedure Button1Click(Sender: TObject);
 private
Â
 public
Â
 end;
Â
var
 Form1: TForm1;
Â
implementation
Â
{$R *.lfm}
Â
{ TForm1 }
Â
procedure TForm1.Button1Click(Sender: TObject);
var a: array of Double;
begin
 a[99]:=3.14;
end;
Â
end.   Â
Â
with GDB: I got exception message box, then I got grayed line in Source Editor etc.
Â
with fpdebug: also exception message box, when I click OK then Lazarus Main window dissapears, Access Violation, and I have to restart whole IDE.
Â
Is it known issue? After all fpdebug is still marked "beta".
Â
PS: Good thing about fpdebug is lower memory footprint.
 fpdebug: process lazarus 137MB
 gdb: process lazarus and gdb 86MB + 184MB = 270MB
Â
Thanks, VojtÄch
when I write following code (to force SIGSEGV)
Â
unit Unit1;
{$mode objfpc}{$H+}
Â
interface
Â
uses
 Classes, SysUtils, Forms, Controls, Graphics, Dialogs, StdCtrls;
Â
type
 { TForm1 }
 TForm1 = class(TForm)
  Button1: TButton;
  procedure Button1Click(Sender: TObject);
 private
Â
 public
Â
 end;
Â
var
 Form1: TForm1;
Â
implementation
Â
{$R *.lfm}
Â
{ TForm1 }
Â
procedure TForm1.Button1Click(Sender: TObject);
var a: array of Double;
begin
 a[99]:=3.14;
end;
Â
end.   Â
Â
with GDB: I got exception message box, then I got grayed line in Source Editor etc.
Â
with fpdebug: also exception message box, when I click OK then Lazarus Main window dissapears, Access Violation, and I have to restart whole IDE.
Â
Is it known issue? After all fpdebug is still marked "beta".
Â
PS: Good thing about fpdebug is lower memory footprint.
 fpdebug: process lazarus 137MB
 gdb: process lazarus and gdb 86MB + 184MB = 270MB
Â
Thanks, VojtÄch