Home | Docs | Forums | Lists | Bugs | Planet | Store | GMN | Get Gentoo!
View Bug Activity | Format For Printing | XML | Clone This Bug
There is a version a20 of cdrecord-ProDVD available, which should be covered by xcdroast. Also, it is no longer available for i586 but have switched to i686. Why is there no seperate ebuild for cdrecord-ProDVD? xcdroast could depend on it in case USE="dvdr" is set. Also, you don't need xcdroast for using cdrecord-ProDVD! Another point: I'm having troubles get xcdroast to work on my amd64 in 64bit mode. It compiles fine but segfaults while starting. Any hints? Also i had no success using cdrecord-ProDVD until now. I've contacted the author of cdrecord-ProDVD concerning a native port for amd64. I'll give you news in case something interessting happens.
a21 is already out now
I added cdrecord-prodvd a24 as a new ebuild to portage. There are also changes in the recent xcdroast-ebuild. For the amd64-error it would be interesting to see the messages. Maybe with an strace or something like this.
Created an attachment (id=24064) [edit] Strace of /xcdroast-0.98_alpha15-r3 executed on amd64 as root(first time) xcdroast keeps segfaulting on amd64, altought it compiles fine. Here is emerge info, strace is the attachment... Portage 2.0.49-r21 (default-amd64-1.4, gcc-3.3.2, glibc-2.3.2-r9, 2.6.1-gentoo-r1) ================================================================= System uname: 2.6.1-gentoo-r1 x86_64 4 Gentoo Base System version 1.4.3.12 ACCEPT_KEYWORDS="amd64" AUTOCLEAN="yes" CFLAGS="-O2" CHOST="x86_64-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.1/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache sandbox" GENTOO_MIRRORS="http://ftp.snt.utwente.nl/pub/os/linux/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="3dnow X alsa amd64 apm arts avi berkdb cdr crypt encode esd foomaticdb gdbm gif gnome gpm gtk gtk2 imlib jpeg libg++ libwww mikmod mmx motif mozilla mpeg multilib ncurses nls nptl oggvorbis opengl oss pam pdflib perl png python quicktime readline sdl slang spell sse ssl tcpd truetype xml2 xmms xv zlib"
I managed to get it running some time ago, but most likely it was just a matter of luck. Could you please analyze the core (using gdb) and check where it segfaults? Is it create_autodiskmount_handler()? If so, your box is also recognized as __APPLE__ (like it was at my side)? Which gcc, glibc etc. are you using?
Which gcc, glibc etc. are you using? >> Check on the comment of my above yours (gdb) run Starting program: /usr/bin/xcdroast (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)... Program received signal SIGSEGV, Segmentation fault. 0x0000000000436dfa in scanbus_new ()
Not exactly, have you run your core file through gdb? Set 'ulimit -c unlimited' to get a core file. I'm looking for something like this (this is my output when i had these problems some weeks ago): Loaded symbols for /usr/X11R6/lib/libXcursor.so.1 Reading symbols from /usr/lib/gtk-2.0/2.2.0/loaders/libpixbufloader-gif.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib/gtk-2.0/2.2.0/loaders/libpixbufloader-gif.so #0 0x00000000004330f9 in create_autodiskmount_handler () (gdb) bt #0 0x00000000004330f9 in create_autodiskmount_handler () #1 0x0000000000433580 in create_autodiskmount_handler () #2 0x00000000004336d3 in scanbus_new () #3 0x000000000043118f in create_device_scanning () #4 0x000000000040ddd2 in main ()
My bad, in that case it looks like the same prob u had. Backtrace was generated from '/usr/bin/xcdroast' (no debugging symbols found)...Using host libthread_db library "/lib/libthread_db.so.1". Core was generated by `xcdroast'. Program terminated with signal 11, Segmentation fault. (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...#0 0x0000000000436dfa in scanbus_new () #0 0x0000000000436dfa in scanbus_new () #1 0x000000000043443a in create_device_scanning () #2 0x000000000040e136 in main () Thread 1 (process 6269): #0 0x0000000000436dfa in scanbus_new () No symbol table info available. #1 0x000000000043443a in create_device_scanning () No symbol table info available. #2 0x000000000040e136 in main () No symbol table info available.
Please note - this crashing bug on AMD64 is fixed for quite a while now. See the patches section on http://www.xcdroast.org/xcdr098/patches
Thanks for the link! I check the xcdroast-patches-website occassionally, but I missed the amd64 patch. I'll enhance the ebuild for it later this day.
Patch added to ebuild (still the 0.98_alpha15-r3). Please test and tell the results.
The patch file needs editing for the r3 ebuild to work correctly as xtools.c2 does not exist. All works fine for me with the edit. --- xtools.c.org 2003-11-06 11:19:10.000000000 +0100 +++ xtools.c2 2004-01-04 14:48:09.000000000 +0100 to --- xtools.c.org 2003-11-06 11:19:10.000000000 +0100 +++ xtools.c 2004-01-04 14:48:09.000000000 +0100
I fixed it in CVS more than 24h ours ago. Should be on the mirrors now. Please try again.
