madExcept refuses work after saving project
Posted: Wed Nov 04, 2015 7:16 pm
On a new VCL project with just one form and almost no function madExcept works on creation if the project ist still in memory.
The only function is an access to an empty TList which must lead to an exception, which it does.
When the project is created the exception immediately following start brings up the usual madExcept screen.
When I save the project to disk, compile and start again, madExcept is lost, I get just the useless delphi exception message.
All settings are ok, madExcept is enabled, the project settings contain madExcept, I see no reason for this strange behaviour.
it happens with Delphi XE7 (madExcept 4.011) and XE8 (madExcept 4.013).
Delphi is installed in a VMWare, storage of the project is on an shared folder on disk of the host OS.
Both OSes are Windows7 Pro.
When the project is saved on a local folder in the VM, madExcept continues working.
When that project is copied to the shared folder and the exe is started from there, madexcept still works.
When that project on the host disk is compiled, madExcept is gone.
Both folders are completely accessible, files can be copied in both directions with no problems.
This is the sourcecode :
##############################################################
unit Unit1;
interface
uses
Winapi.Windows, Winapi.Messages, System.SysUtils, System.Variants, System.Classes, Vcl.Graphics,
Vcl.Controls, Vcl.Forms, Vcl.Dialogs;
type
TForm1 = class(TForm)
procedure FormCreate(Sender: TObject);
private
{ Private-Deklarationen }
public
{ Public-Deklarationen }
end;
var
Form1: TForm1;
implementation
{$R *.dfm}
procedure TForm1.FormCreate(Sender: TObject);
var
l: TList;
f: TForm;
begin
l := Tlist.Create;
f := l[0];
end;
end.
##############################################################
Regards
Gerhard Sachs
The only function is an access to an empty TList which must lead to an exception, which it does.
When the project is created the exception immediately following start brings up the usual madExcept screen.
When I save the project to disk, compile and start again, madExcept is lost, I get just the useless delphi exception message.
All settings are ok, madExcept is enabled, the project settings contain madExcept, I see no reason for this strange behaviour.
it happens with Delphi XE7 (madExcept 4.011) and XE8 (madExcept 4.013).
Delphi is installed in a VMWare, storage of the project is on an shared folder on disk of the host OS.
Both OSes are Windows7 Pro.
When the project is saved on a local folder in the VM, madExcept continues working.
When that project is copied to the shared folder and the exe is started from there, madexcept still works.
When that project on the host disk is compiled, madExcept is gone.
Both folders are completely accessible, files can be copied in both directions with no problems.
This is the sourcecode :
##############################################################
unit Unit1;
interface
uses
Winapi.Windows, Winapi.Messages, System.SysUtils, System.Variants, System.Classes, Vcl.Graphics,
Vcl.Controls, Vcl.Forms, Vcl.Dialogs;
type
TForm1 = class(TForm)
procedure FormCreate(Sender: TObject);
private
{ Private-Deklarationen }
public
{ Public-Deklarationen }
end;
var
Form1: TForm1;
implementation
{$R *.dfm}
procedure TForm1.FormCreate(Sender: TObject);
var
l: TList;
f: TForm;
begin
l := Tlist.Create;
f := l[0];
end;
end.
##############################################################
Regards
Gerhard Sachs