Quoting Udo Rader <[EMAIL PROTECTED]>:

> Am Mon, 11 Aug 2003 00:20:49 +0000 schrieb Leon Brooks:
> 
> > On Mon, 11 Aug 2003 07:32, Udo Rader wrote:
> >> seems to be some kind of cdrecord issue as this is the last thing
> >> that xcdroast tries to access, see the following strace excerpt:
> > 
> >> ------CUT-------
> >> fstat64(6, {st_mode=S_IFIFO|0600, st_size=0, ...}) = 0 mmap2(NULL,
> >> 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
> >> 0x4048a000 read(6, "Linux sg driver version: 3.1.25\n", 4096) = 32
> >> read(6, "Cdrecord 2.01a16-dvd (i586-mandr"..., 4096) = 599 ---
> >> SIGSEGV (Segmentation fault) @ 0 (0) --- +++ killed by SIGSEGV +++
> >> ------CUT-------
> > 
> > I'm betting on a change in output format for cdrecord. If so, xcdroast 
> > needs a wrist-slap for fragility. Do you have an older version handy to 
> > compare outputs with?
> > 
> > Cheers; Leon
> 
> yes, cdrecord is the bad boy. I have no older version ready but it works
> with the current rawhide (=redhat cooker) release (cdrecord and cdda2wav
> 2.0-11.1).
> 

the bad boy is xcdroast, not cdrecord.
i have the impression that when the cdrecord version changes
xcdroast starts to segfaults, could it be that the cdrecord version is 
hardcoded somewhere in xcdroast?

anyway you might want to try :
http://varna.demon.co.uk/~svetlio/ruby-contrib/mdk-cook/cdrecord-2.01-0.a18.1mdk.src.rpm
http://varna.demon.co.uk/~svetlio/ruby-contrib/mdk-cook/xcdroast-0.98-28.alpha14mdk.src.rpm

svetljo


Reply via email to