OnClick SIGSEVG Exception

[pmesquita]

Personal..
I have a problem here that I don't know anymore what it could be...

I have a Form (fsMDIForm) where when I click on the TSpeedButton button, all the OnClick event routines are executed (basically it is an SQL that authenticates the user in the database) but when debugging, when executing the entire Begin/End block, an exception SIGSEVG is generated ..

Through CallStack I saw that the error is on line 2911 of control.inc

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

1.  
2. procedure TControl.Click;
3.  
4.   function OnClickIsActionExecute: boolean;
5.   begin
6.     Result:=false;
7.     if Action=nil then exit;
8.     if not Assigned(Action.OnExecute) then exit;
9.     if not Assigned(FOnClick) then exit;
10.     Result:=CompareMethods(TMethod(FOnClick),TMethod(Action.OnExecute));
11.   end;
12.  
13. var
14.   CallAction: Boolean;
15. begin
16.   //DebugLn(['TControl.Click ',DbgSName(Self)]);
17.   CallAction:=(not (csDesigning in ComponentState)) and (ActionLink <> nil);
18.  
19.   // first call our own OnClick if it differs from Action.OnExecute
20.   if Assigned(FOnClick)
21.   and ((not CallAction) or (not OnClickIsActionExecute)) then
22. [b]    FOnClick(Self);[/b]
23.   // then trigger the Action
24.   if CallAction then
25.     ActionLink.Execute(Self);
26. end;
27.  

Windows 10 x64
Lazarus 2.0.12
FPC 3.2.0
Build Mode: Debug


Any idea what it might be or any tips from how can i debug...?

[ADMGNS]

hello

as my experience, compare with nil have potantial problems.. instead of, kindly you must use 'assigned' always to check..

regs

[Bart]

Assigned just checks for nil...

[MarkMLl]

Assigned just checks for nil...

Except where it's checking whether a function returning a pointer (etc.) is assigned, in which case it /specifically/ looks at the function rather than evaluating it and looking at the result.

MarkMLl

[jamie]

I don't know, I see trouble ahead using Assigned to validate pointers from a function, that is directly wrapping it around a function.

[lucamar]

I don't know, I see trouble ahead using Assigned to validate pointers from a function, that is directly wrapping it around a function.

I think what Mark means is validating a var of a procedural type pointing to a function returning a pointer, such as:

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

1. type
2.   APtrFunction = function: Pointer;
3.  
4. var
5.   TheFunction: APtrFunction;
6.  
7. {...}
8.  
9.   if Assigned(TheFunction) then
10.     { ... };

In that specific case Assigned() is guaranteed to check if the var TheFunction is Nil, rather than whether the result of a call to it returns Nil.

I don't remember where I read that, though; sorry.

[MarkMLl]

I don't know, I see trouble ahead using Assigned to validate pointers from a function, that is directly wrapping it around a function.

I think what Mark means is validating a var of a procedural type pointing to a function returning a pointer, such as:

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

1. type
2.   APtrFunction = function: Pointer;
3.  
4. var
5.   TheFunction: APtrFunction;
6.  
7. {...}
8.  
9.   if Assigned(TheFunction) then
10.     { ... };

In that specific case Assigned() is guaranteed to check if the var TheFunction is Nil, rather than whether the result of a call to it returns Nil.

I don't remember where I read that, though; sorry.

Yes, that's what I mean. It's a consequence of Pascal (unlike Modula-2 and C) not distinguishing between a (pointer to) a function and the result of the function's invocation by whether the function name is followed by parentheses.

MarkMLl