Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#16200 - [gavl] causes SIGILL (tuned to specific cpu)
Attached to Project:
Community Packages
Opened by Michael Witten (mfwitten) - Tuesday, 15 September 2009, 05:35 GMT
Last edited by Ionut Biru (wonder) - Saturday, 03 October 2009, 22:04 GMT
Opened by Michael Witten (mfwitten) - Tuesday, 15 September 2009, 05:35 GMT
Last edited by Ionut Biru (wonder) - Saturday, 03 October 2009, 22:04 GMT
|
DetailsDescription:
----------- Simply put, the `gavl' package needs to be recompiled with generic x86 gcc flags. The `gavl' package, last built on 2009-01-22, causes SIGILL on my pentium-M machine. SIGILL is a rare error caused when a program tries to execute a malformed, unknown, or privileged instruction, which is usually the result of an improperly compiled binary. In this case, I'm pretty sure that the maintainer (or whatever compiles gavl) performed the compilation with gcc instructed to tune the code to a specific CPU/architecture, thereby rendering it useless to others. I came across this problem essentially because gstreamer was failing to initialize and reporting "Error initializing: Error re-scanning registry , child terminated by signal". __tim at #gstreamer had me run: gdb --args gst-launch-0.10 --gst-disable-segtrap --gst-disable-registry-fork which produced (after running `run' and then maybe `bt' in gdb): SIGILL in gavl_video_scale_table_init () from /usr/lib/libgavl.so.1 I then came across this thread: http://bbs.archlinux.org/viewtopic.php?pid=618752 in which Svenstaro mentions that recompiling gavl locally fixed the problem; Svenstaro wrote "Fixed by recompiling gavl v1.1.1 using proper -mtune settings. It appears this bugs only occurs to people with a lower CPU than the gavl maintainer." |
This task depends upon
Closed by Ionut Biru (wonder)
Saturday, 03 October 2009, 22:04 GMT
Reason for closing: Fixed
Additional comments about closing: gavl-1.1.1-2
ask for re-open if needed
Saturday, 03 October 2009, 22:04 GMT
Reason for closing: Fixed
Additional comments about closing: gavl-1.1.1-2
ask for re-open if needed