[k3b] [Bug 137436] Adding support for cdrskin as an alternative to cdrecord/wodim

[Leslie Zhai]

https://bugs.kde.org/show_bug.cgi?id=137436

--- Comment #73 from Leslie Zhai <xiangzhai83 at gmail.com> ---
(In reply to Thomas Schmitt from comment #72)
> Hi,
> 
> > It is better to use Clang ThreadSanitizer to detect pthread related issue
> 
> I currently see no indication that the problem with CDEmu is related to
> pthreads.

Never mind ;-) it might be Clang's issue ;-P such as:
https://llvm.org/bugs/show_bug.cgi?id=31304
https://llvm.org/bugs/show_bug.cgi?id=28331
https://llvm.org/bugs/show_bug.cgi?id=15836
https://llvm.org/bugs/show_bug.cgi?id=31017


> The refusal of CDEmu on RESERVE TRACK probably stems from
>  
> https://sourceforge.net/p/cdemu/code/ci/master/tree/cdemu-daemon/src/device-
> commands.c
> function command_reserve_track in line 2199.
> One would have to find possible reasons for the two refusals with
>   cdemu_device_write_sense(self, ILLEGAL_REQUEST, COMMAND_SEQUENCE_ERROR);
> in order to learn how to avoid them.
> 
> About the reply of sg_io_hdr_t.host_status == 1 and the errno == 19
> i cannot say much. That's deeper inside the kernel's device driver
> architecture than i ever had to climb down.
> 
> As said, i cannot exclude the possibility that some of libburn's activities
> cause these problems with CDEmu. But i have no such experiences with my
> own drives and got no such reports from other users of real drives.

I will report bug to CDEmu ;-)

Regards,
Leslie Zhai

-- 
You are receiving this mail because:
You are the assignee for the bug.