Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Segmentation Fault when launching roseus in 16.04 #291

Closed
Affonso-Gui opened this issue Jul 12, 2018 · 8 comments
Closed

Segmentation Fault when launching roseus in 16.04 #291

Affonso-Gui opened this issue Jul 12, 2018 · 8 comments

Comments

@Affonso-Gui
Copy link
Member

When using the latest versions for jskeus (euslisp/jskeus@fa7b88f) and eus (d7a3284) from source in Ubuntu 16.04, running roseus leads to:

roseus ;; Segmentation Fault.
;; in (load-library "roseus.so" '("roseus"))
;; You are still in a signal handler.
;;Try reset or throw to upper level as soon as possible.
;; code=1757534960 x=68c1d9c0 addr=5

This problem does not occur in Ubuntu 14.04 nor when using eus version 1f5a9e9.

Verified the above in a total of 5 PCs (three of them 16.04, two of them 14.04).
@weiqiyang
@itohdak

@YoheiKakiuchi
Copy link
Member

roseus may be compiled with (euslisp/jskeus@fa7b88f)
(I do not test yet)

@Affonso-Gui
Copy link
Member Author

Affonso-Gui commented Jul 12, 2018

using roseus from apt seemed to be the reason for this. (conflicting definitions in eus.h)

Still testing, but seems that compiling roseus from source too does the job.

@YoheiKakiuchi
Copy link
Member

Please test with these PR
#292
jsk-ros-pkg/jsk_roseus#568

@Affonso-Gui
Copy link
Member Author

Was able to build and launch with the PR above. The remaining question is why does it work on 14.04 and not in 16.04? roseus version seems to be the same for both systems.

rosversion roseus
1.6.3

@Affonso-Gui
Copy link
Member Author

Also, in roseus.cpp it appears that we already had an optional documentation parameter using _defun (https://github.com/jsk-ros-pkg/jsk_roseus/blob/master/roseus/roseus.cpp#L1878-L1883)

Using _defun seemed more clear to me than using the #undef - #define schematics. Is this open to discussion?

@k-okada

@k-okada
Copy link
Member

k-okada commented Jul 12, 2018

@Affonso-Gui I think it also fails on indigo

https://travis-ci.org/jsk-ros-pkg/jsk_roseus/builds/402501419

indigo-fail

@Affonso-Gui
Copy link
Member Author

Resuming:

  • Segmentation fault is due to different eus.h versions between euslisp and roseus.
  • Is solved by compiling roseus from source.

#111

@Affonso-Gui
Copy link
Member Author

Just for the record:
instructions to compile both roseus & euslisp from source can be found in https://github.com/jsk-ros-pkg/jsk_roseus#use-roseus-with-euslisp-built-from-source

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants