| Summary: | pycam (media-gfx/pycam-0.6.2)get's SIGSEGV from libglut.so.3 (media-libs/freeglut-3.0.0) | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | alex Mezey <gentoobugs> |
| Component: | Current packages | Assignee: | Gentoo X packagers <x11> |
| Status: | RESOLVED NEEDINFO | ||
| Severity: | normal | CC: | jstein |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
alex Mezey
2017-12-26 15:33:16 UTC
Thank you for the report. Please *attach* the logfiles, https://wiki.gentoo.org/wiki/Attach_the_logs_to_the_bug_ticket and reopen this ticket (Status:unconfirmed). Pycam does not make any logs at startup. It's a runtime Error, not during build. Thats why I posted gdb output. I don't know much about gdb. So I don't even know wether this is a bug in pycam, freeglut or in python 2.7.14-r1 If the bug is in pycam, which is entirely written in python, I should get an error message by the python interpreter instead of a segfault, I guess. The packages dev-python/pyopengl-3.1.0 and dev-python/pyopengl-accelerate-3.1.0 can contain the bug as they are involved, compiled code and link to the actual opengl libraries. To me it sounds like a bug in the software provided upstream or a misconfiguration in your system [3]. Does the same source work for you on another distribution? If it works on other distributions, but not on Gentoo Linux, I suggest to discuss this problem on a related mailing list, forum or IRC channel. I have had very good experience on the Gentoo IRC [1], of course there are also forums and mailing lists. [2] I will close this bug here, because I do not see a relation to the gentoo ebuild or the way Gentoo handles this special software package. Please provide more information, if I am wrong. [1] https://www.gentoo.org/get-involved/irc-channels/ [2] https://www.gentoo.org/support/ [3] look up the upstream forums; search in their bug tracker |