Ubuntu
ffmpeg package

SIGSEGV in gxine on iBook G4

Bug #163527 reported by Remove Me
2
Affects Status Importance Assigned to Milestone
ffmpeg (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Happens when opening an avi. The file is on NFS, but it doesn't seem to be the problem.
System is iBook G4, Kernel 2.6.22.6. Nothing unusual in syslog/dmesg.

(gdb) r dva.kapitana.cd2.avi
Starting program: /usr/bin/gxine dva.kapitana.cd2.avi
[Thread debugging using libthread_db enabled]
[New Thread 805475136 (LWP 3325)]
[New Thread 813917392 (LWP 3328)]
[New Thread 824427728 (LWP 3329)]
[New Thread 833086672 (LWP 3330)]
[New Thread 845714640 (LWP 3331)]
[New Thread 858203344 (LWP 3332)]
[New Thread 868480208 (LWP 3333)]
[New Thread 907904208 (LWP 3336)]
[New Thread 916292816 (LWP 3337)]
[New Thread 916554960 (LWP 3338)]
lirc: cannot initialise - disabling remote control
lirc: maybe lircd isn't running or you can't connect to the socket?
[New Thread 929182928 (LWP 3339)]
[Thread 916554960 (LWP 3338) exited]
[New Thread 937841872 (LWP 3340)]
CDROMREADTOCHDR: Input/output error
WARN: could not retrieve file info for `image.nrg': No such file or directory
WARN: can't open nrg image file image.nrg for reading
[New Thread 946230480 (LWP 3341)]
[New Thread 946492624 (LWP 3342)]
[New Thread 965465296 (LWP 3343)]
[Thread 946492624 (LWP 3342) exited]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 858203344 (LWP 3332)]
0x0e71493c in avg_pixels8_altivec () from /usr/lib/libavcodec.so.1d
(gdb) bt
#0 0x0e71493c in avg_pixels8_altivec () from /usr/lib/libavcodec.so.1d
#1 0x0e49b43c in MPV_motion () from /usr/lib/libavcodec.so.1d
#2 0x0e49d9c8 in MPV_decode_mb () from /usr/lib/libavcodec.so.1d
#3 0x0e5ce1fc in decode_slice () from /usr/lib/libavcodec.so.1d
#4 0x0e5cf6ac in ff_h263_decode_frame () from /usr/lib/libavcodec.so.1d
#5 0x0e4848f8 in avcodec_decode_video () from /usr/lib/libavcodec.so.1d
#6 0x0e83ed54 in ?? () from /usr/lib/xine/plugins/1.1.7/xineplug_decode_ff.so
#7 0x0ff7b260 in ?? () from /usr/lib/libxine.so.1
#8 0x0f5e8b14 in start_thread () from /lib/libpthread.so.0
#9 0x0f37e7e4 in clone () from /lib/libc.so.6
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
(gdb)

Revision history for this message
Remove Me (remove-me) wrote :

Regarding ffmpeg: ffplay works perfectly with the file.

Revision history for this message
Reinhard Tartler (siretart) wrote :

Thanks for taking your time to report this bug. You have reported a crash in the ffmpeg library. In order to be able to actually fix this bug, we must be able to

  * reproduce it
  * check if it happens with the latest version
  * understand where it actually crashes

You can help with the first point by attaching an example file to this bug report. Please note that a proper attachment is preferred over a link to some remote site. Remote side that are password protected or otherwise restriced (like services like rapidshare.com and similar) are absolutely not acceptable.

For the 2nd point, the MOTUMedia team provide updated packages for xine-lib and ffmpeg in their PPA for past ubuntu releases. See http://launchpad.net/~motumedia/+archive for instructions how to enable that archive. Please add this repository to your /etc/apt/sources.list, update your system and make sure, that you have the package 'ffmpeg-dbg' installed (use 'sudo apt-get dist-upgrade && sudo apt-get install ffmpeg-dbg'). This way, you can produce meaningful backtraces that help us with point 3. You can read https://wiki.ubuntu.com/Backtrace about how to create proper backtraces that help developers identifying the exact location of the crash. Please make sure that you always report the exact version of the package that you are testing. This information can be obtained using the command 'dpkg -l ffmpeg-dbg'.

Thank you for your cooperation.

Changed in ffmpeg:
status: New → Incomplete
Revision history for this message
Remove Me (remove-me) wrote :

I'm sorry, but the system is not available to me anymore.

Revision history for this message
Reinhard Tartler (siretart) wrote :

okay, in this case I have to invalidate this bug. sorry :(

Changed in ffmpeg:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.