Home | Docs | Forums | Lists | Bugs | Planet | Store | GMN | Get Gentoo!

Full Text Bug Listing

Please patch xvid-1.0.2's sources to work on 64bit platforms.
1.0.1 shows an example. That patch doesn't work on 1.0.2 unfortunately.
Cheers,
Marc.

Reproducible: Always
Steps to Reproduce:
emerge xvid-1.0.2 on 64-bit platforms
Actual Results:

Hi herd!
Kugelfang will take a look at this.

1.0.1 is unstable on amd64, too.
I emerged 1.0.2, discovered it segfaults, found this bug report, and emerged 1.0.1 in hopes it would work, but it segfaults in the same manner (and also has jerky framerate compared to the old 0.9.1).

Observations:
1.  using default configuration in transcode will cause a segfault during DVD transcoding.  In my case it occurs after about 6000 frames.
2.  enabling quarter pel in the config file causes a segfault within 40 frames.

Command line used:
transcode -i /dev/dvd -x dvd -f 29.970 -I 5 -w 800 -y xvid4 -o myfile_xvid4_1pass_qpeltrellisbframe_800.avi -z

Sample problem:

libdvdread: Found 1 VTS's
libdvdread: Elapsed time 0
[encoder.c] Delaying audio (0)
[encoder.c] Delaying audio (0)],  43.20 fps, EMT: 0:00:00, ( 0| 0| 1)
encoding frames [000000-006536],   6.79 fps, EMT: 0:03:38, ( 0| 0| 0)
clean up | frame threads | unload modules | cancel signal | internal threads | done
[transcode] encoded 6537 frames (0 dropped, 0 cloned), clip length 218.12 s

And if we enable quarterpel:
[encoder.c] Delaying audio (0)
[encoder.c] Delaying audio (0)],  53.23 fps, EMT: 0:00:00, ( 0| 1| 1)
Segmentation fault00000-000040],  19.24 fps, EMT: 0:00:01, ( 0| 0| 9)

My emerge info is:
Portage 2.0.50-r11 (default-amd64-2004.2, gcc-3.3.4, glibc-2.3.4.20040808-r0, 2.6.7)
=================================================================
System uname: 2.6.7 x86_64 5
Gentoo Base System version 1.4.16
Autoconf: sys-devel/autoconf-2.59-r4
Automake: sys-devel/automake-1.8.5-r1
ACCEPT_KEYWORDS="amd64"
AUTOCLEAN="yes"
CFLAGS="-O2 -pipe"
CHOST="x86_64-pc-linux-gnu"
COMPILER=""
CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/mozilla/defaults/pref /usr/share/config /var/qmail/control"CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O2 -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs ccache"
GENTOO_MIRRORS="http://gentoo.osuosl.org http://distro.ibiblio.org/pub/Linux/distributions/gentoo"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="X aac alsa amd64 apm audiofile avi berkdb bitmap-fonts bonobo cdr chroot crypt cups dga dnd dv dvd dvdr encode esd faad ffmpeg flac foomaticdb freetype gdbm gif gimpprint glade gnome gphoto2 gpm gtk gtk2 icq ieee1394 imlib joystick jpeg libg++ libwww lufsusermount mad matroska mikmod mng motif mozilla mpeg mpeg4 multilib ncurses nogcj oggvorbis opengl openssh oss pam pdflib perl png pthreads python quicktime readline samba sdl slang spell ssl tcltk tcpd theora tiff transcode truetype usb xine xml2 xmms xprint xv xvid zlib"

Sorry, I forgot to add the -T 1,-1 argument to the command line, and that fixes
the 6000 frame stoppage.  ;-)

But I still contend that quarterpel = 1 causes a segfault even in xvid-1.0.1.

The patch has now been added to xvid-1.0.2.ebuild (as of 3 Oct.), but with one
minor issue:  there's a typo in the ebuild that prevents the patch from being
applied.

Line 27 of the ebuild reads:
 epatch ${FILESIDR}/${PN}-1.0.1-64bit-clean.patch

Should be:
 epatch ${FILESDIR}/${PN}-1.0.1-64bit-clean.patch

I don't use a 64-bit platform, so I can't verify if the patch does what it's
supposed to do, but the ebuild applies the patch on all architectures.

Thanks for the hint. Looks like someone was in a hurry. I guess this can be
closed, then?

I did an emerge sync, emerged the 1.0.2 ebuild, and first pass encoding no
longer segfaults (good!) but then I tried quarterpel again.  It still segfaults
on amd64.  Should this be filed as a different bug?  It looks like no patch has
addressed this before since it also affects 1.0.1.  Thanks!