You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What is happening:
The newcoords method is using a macro slot accessor without checking the class of the argument. https://github.com/euslisp/EusLisp/blob/master/lisp/l/coordinates.l#L58-L62
When on interpreter the object class is verified, but when compiled this is replaced by a simple address, which could be any value or a null pointer, thus causing the segmentation fault.
Possible solutions
We could add a coordinates-p check, use the dot accessor (which is translated differently and still works normally after compiled), or update the compiler to verify the classes at macro accessors.
How to reproduce:
What is happening:
The newcoords method is using a macro slot accessor without checking the class of the argument. https://github.com/euslisp/EusLisp/blob/master/lisp/l/coordinates.l#L58-L62
When on interpreter the object class is verified, but when compiled this is replaced by a simple address, which could be any value or a null pointer, thus causing the segmentation fault.
Possible solutions
We could add a
coordinates-p
check, use the dot accessor (which is translated differently and still works normally after compiled), or update the compiler to verify the classes at macro accessors.@a-ichikura
jsk-ros-pkg/euslime#5
The text was updated successfully, but these errors were encountered: