Hello,
On Sun, Mar 20, 2011 at 9:58 AM, Ludovic Rousseau
<[email protected]> wrote:
> Hi,
>>>> Hello,
>>>
>>> I fixed the valgrind warning in revision 5659.
>>> I would be surprised if that was the cause of the crash.
>>>
>>
>> I just had a segfault again. This time glibc was so nice to print a
>> backtrace.
>> First, I get endless of these:
>> 00000987 ccid_usb.c:618:WriteUSB() write failed (6/42): -99 Success
>> 00000454 ccid_usb.c:618:WriteUSB() write failed (6/42): -99 Success
>>
>> And then the segfault.
>> Its a pcscd 1.6.7.
>>
>> I have copied all of the backtrace, maybe that is helpfull.
>> Is it possible that the segfault is triggered by my app?
>
> No. The crash is in pcscd. It is not a bug in your application.
>
> I would suspect libusb-1.0.
> Many bugs have been corrected in the git repository but a new release
> of libusb is not yet available.
> Can you get the git version of libusb and try again?
I have donwloaded current git and used pcscd 1.7.0.
This time its a bit different:
00000018 APDU: 80 1C 00 00 00
00000016 ifdhandler.c:1280:IFDHTransmitToICC()
usb:0529/0620:libudev:0:/dev/bus/usb/006/049 (lun: 0)
06139786 ccid_usb.c:657:ReadUSB() read failed (6/49): -99 Success
00000044 openct/proto-t1.c:214:t1_transceive() fatal: transmit/receive failed
00000023 SW:
00000016 ifdwrapper.c:525:IFDTransmit() Card not transacted: 612
00000015 winscard.c:1576:SCardTransmit() Card not transacted: 0x80100016
00000015 winscard_svc.c:602:ContextThread() TRANSMIT rv=0x80100016 for client 12
Segmentation fault
I will see if I can find out more.
Maybe its my application.
Its doing int the area of the segfault:
start:SC_BEGIN_TRANSACTION
return:SC_BEGIN_TRANSACTION
start:SC_TRANSMIT
PCSC: SCardTransmit_pcsc-> Failure: Transaction failed. (0x80100016)
SCARD: TS_SCardTransmit-> Failure: Transaction failed. (0x80100016)
Failure: Transaction failed. (0x80100016) TS_SCardTransmit
return:SC_TRANSMIT
The Transmit call allocates some buffers, maybe there is some error in it.
Martin
_______________________________________________
Muscle mailing list
[email protected]
http://lists.drizzle.com/mailman/listinfo/muscle
