Re: [Libusbx-devel] libusb segfaults - causes pcscd to crash

On 06.09.2012 00:45, Pete Batard wrote: > We haven't seen crash reports from you since we pushed the fixes that > (we hoped) could address the issue. Can you confirm that you've been > happily running pcscd ever since? Hello Pete, sorry for my delayed response. I have been out of office for a

Re: [Libusbx-devel] libusb segfaults - causes pcscd to crash

Hi Sebastian, We haven't seen crash reports from you since we pushed the fixes that (we hoped) could address the issue. Can you confirm that you've been happily running pcscd ever since? Regards, /Pete -- Live Secur

Re: [Libusbx-devel] libusb segfaults - causes pcscd to crash

On 2012.08.27 09:03, Ludovic Rousseau wrote: >> How do you propose we address this in libusbx? > > Don't change anything in libusbx. Well, I think at least a doc change is in order, to let daemon writers know that they may have to contend with output from libusbx to descriptor #2, even after the

Re: [Libusbx-devel] libusb segfaults - causes pcscd to crash

2012/8/27 Pete Batard : > On 2012.08.24 10:10, Ludovic Rousseau wrote: >> I already reported the issue in 2008 in "A library shall not write to >> stderr or stdout without explicit request" [1]. > > "So unless explicitly requested the library shall not send anything to > stdout or stderr." > > How

Re: [Libusbx-devel] libusb segfaults - causes pcscd to crash

On 2012.08.24 10:10, Ludovic Rousseau wrote: > I already reported the issue in 2008 in "A library shall not write to > stderr or stdout without explicit request" [1]. "So unless explicitly requested the library shall not send anything to stdout or stderr." How do you propose we address this in li

Re: [Libusbx-devel] libusb segfaults - causes pcscd to crash

2012/8/23 Pete Batard : > On 2012.08.23 12:57, sebastiank wrote: >> Pcscd does not function as expected, i.e. my app is not able to find >> the attached rfid-reader, although pcscd is recognising it and is >> logging the card insertion and removal. >> >> This is happening, when pcscd is started as

Re: [Libusbx-devel] libusb segfaults - causes pcscd to crash

On 2012-08-23 21:51, Pete Batard wrote: > Could be a problem with output redirection in pcscd then, rather than a > libusbx issue. The only component that has been altered is libusbx. I did the lib compiling the same way I did the last several weeks. So indeed, it was surprising. Just wanted to inf

Re: [Libusbx-devel] libusb segfaults - causes pcscd to crash

On 2012.08.23 12:57, sebastiank wrote: > Pcscd does not function as expected, i.e. my app is not able to find > the attached rfid-reader, although pcscd is recognising it and is > logging the card insertion and removal. > > This is happening, when pcscd is started as daemon and > > - LIBUSB_D

Re: [Libusbx-devel] libusb segfaults - causes pcscd to crash

On 2012-08-22 23:16, Pete Batard wrote: > I have now pushed Peter's patch... THANK YOU VERY MUCH TO ALL OF YOU!!! I have distributed the new version to the prod machines today. While testing the new version (git mainline 1.0.12.10553) on the test machine, I recognised the following strange behavi

Re: [Libusbx-devel] libusb segfaults - causes pcscd to crash

Well, that was really a one in a billion issue (or more realistically a one in a million, as I doubt one actually gets nanosec level timer resolution during code execution, even on the fastest machine). I have now pushed Peter's patch, amended to fix the other location where we were using a > i

Re: [Libusbx-devel] libusb segfaults - causes pcscd to crash

Hello Peter, On 22.08.2012 10:39, Peter Stuge wrote: > Here's a patch to fix that bug, but I'm not sure if it is enough to > completely solve the problem. thank you for the patch. I hope that it will solve it. = Regards Sebastian =

Re: [Libusbx-devel] libusb segfaults - causes pcscd to crash

sebastiank wrote: > libusbx: warning [add_to_flying_list] failed to arm first timerfd (errno 22, > it_value = 259823:10) Here's a patch to fix that bug, but I'm not sure if it is enough to completely solve the problem. //Peter >From 3b821d0a709c6b5b3094a763bb04e48ed0447050 Mon Sep 17 00

Re: [Libusbx-devel] libusb segfaults - causes pcscd to crash

On 16.08.2012 22:46, Pete Batard wrote: > If you're using the version of libusbx with the latest patches, we > will get the needed inisght about the cause for the error. I'm using the latest git-mainline version of libusbx on all machines, with the extra debugging output you advised me to include.

Re: [Libusbx-devel] libusb segfaults - causes pcscd to crash

On 16 August 2012 12:46, sebastiank wrote: > The test machine is still running with LIBUSB_DEBUG set to 4. Do you > know how you will do that? If you're using the version of libusbx with the latest patches, we will get the needed inisght about the cause for the error. > It is unlikely that the e

Re: [Libusbx-devel] libusb segfaults - causes pcscd to crash

On 2012.08.15 23:18, Pete Batard wrote: > By the looks of it, the error you got on the test environment isn't the > same as the one you get in prod, though I still wouldn't mind figuring > out the cause of what happened in test. The test machine is still running with LIBUSB_DEBUG set to 4. Do you k

Re: [Libusbx-devel] libusb segfaults - causes pcscd to crash

On 2012.08.15 08:44, sebasti...@gmx-topmail.de wrote: > Just to verify that I did it right: > I added the following line to /etc/init.d/pcscd, before the pcsc daemon > gets started -> > export LIBUSB_DEBUG=2 2 is indeed warning and as far as I could see, pcscd doesn't redirect or suppress stderr

Re: [Libusbx-devel] libusb segfaults - causes pcscd to crash

> On 2012.08.13 11:00, sebastiank wrote: > > On 2012.08.12 23:59, Pete Batard wrote: > > Patch has now been pushed to the mailine git libusbx repository (along > > with other minor changes. See > > https://github.com/libusbx/libusbx/commits/master for details. > Thank you very much! The new version

Re: [Libusbx-devel] libusb segfaults - causes pcscd to crash

> On 2012.08.12 23:59, Pete Batard wrote: > Patch has now been pushed to the mailine git libusbx repository (along > with other minor changes. See > https://github.com/libusbx/libusbx/commits/master for details. Thank you very much! The new version is now active on the production machines, along w

Re: [Libusbx-devel] libusb segfaults - causes pcscd to crash

> On 2012.08.10 08:53, sebasti...@gmx-topmail.de wrote: >> I'd prefer to wait for your patch, just in case there are more changes Patch has now been pushed to the mailine git libusbx repository (along with other minor changes. See https://github.com/libusbx/libusbx/commits/master for details. R

Re: [Libusbx-devel] libusb segfaults - causes pcscd to crash

On 2012.08.10 08:53, sebasti...@gmx-topmail.de wrote: > Some weeks ago, at the very beginning of our > investigation, I had set the LIBUSB_DEBUG variable to 3 on the production > machines, but it had no impact on the error logging. This would indicate that the error you got on test is different fr

Re: [Libusbx-devel] libusb segfaults - causes pcscd to crash

> On 2012.08.09 22:25, Pete Batard wrote: > OK, first thing I notice is that the timerfd report is output as a > warning rather than debug, so if your test machine is behaving the same > way as your other server, it means that you have silenced warnings > there, which I'd strongly recommend against

Re: [Libusbx-devel] libusb segfaults - causes pcscd to crash

On 2012.08.09 11:31, sebasti...@gmx-topmail.de wrote: > Maybe we got the jackpot (at least I hope so)?! My test computer finally > showed the segmentation fault today morning. Good. The more data we get, the better we'll be able to fix the issue. > You'll find all information in the attached fil

Re: [Libusbx-devel] libusb segfaults - causes pcscd to crash

On 2012.08.07 14:47, sebasti...@gmx-topmail.de wrote: > Just for information: > I got another core dump with the libusbx compiled on monday. > Are you interested in this one? It breaks at the same location, so it will provide the same information as what we already know. Just to confirm, you may

Re: [Libusbx-devel] libusb segfaults - causes pcscd to crash

Just for information: I got another core dump with the libusbx compiled on monday. Are you interested in this one? Program terminated with signal 11, Segmentation fault. #0 0x00115e89 in add_to_flying_list (transfer=0xb5600468) at io.c:1175 1175io.c: Datei oder Verzeichnis nicht gefunden.

Re: [Libusbx-devel] libusb segfaults - causes pcscd to crash

On 2012.08.07 13:00, sebasti...@gmx-topmail.de wrote: >> On 2012.08.07 12:44, Pete Batard wrote: >> Did you get the impression that crash happened sooner than the previous >> ones this time around, or what is about the same? > Very hard to say. To me it seems that the failure occurs totally > rando

Re: [Libusbx-devel] libusb segfaults - causes pcscd to crash

> On 2012.08.07 12:44, Pete Batard wrote: > Did you get the impression that crash happened sooner than the previous > ones this time around, or what is about the same? Very hard to say. To me it seems that the failure occurs totally randomly. Sometimes after some hours, sometimes after several day

Re: [Libusbx-devel] libusb segfaults - causes pcscd to crash

On 2012.08.07 08:30, sebasti...@gmx-topmail.de wrote: Please see the attached file with a new backtrace of the segmentation fault. The file contains all of the commands you told me to execute last week. Thanks for the report. Did you get the impression that crash happened sooner than the previ

Re: [Libusbx-devel] libusb segfaults - causes pcscd to crash

Good morning Pete, Ludovic and Orin, yesterday, I recompiled the latest libusbx version from the git repository with debug information (version 1.0.12.10545) and replaced it on the computers. > On 2012.08.03 15:51, Pete Batard wrote: > If you do observe the crash again, and since you're recompil

Re: [Libusbx-devel] libusb segfaults - causes pcscd to crash

Hi, > On 2012.08.03 15:51, Pete Batard wrote: > Sebastian, > > can you try recompiling and installing libusbx from the latest git version? I'll try to recompile and replace libusbx on Monday. > On 2012.08.03 15:51, Pete Batard wrote: > If you do observe the crash again, and since you're recompil

Re: [Libusbx-devel] libusb segfaults - causes pcscd to crash

> list_for_each_entry() uses next as it steps through the list. > list_for_each_entry_safe() avoids the problem by getting and saving the > next pointer in a temporary before the loop body. Ah right. I misread what you wrote and thought there was another issue at hand there. Your patch looks good

Re: [Libusbx-devel] libusb segfaults - causes pcscd to crash

On Thu, Aug 2, 2012 at 1:58 PM, Pete Batard wrote: > > > Setting next and prev to NULL in list_del() caused a crash in > > usbi_cond_destroy() in threads_windows.c (next was used after calling > > list_del). Using list_for_each_entry_safe fixed it and cleaned up the > code. > > > > int usbi_cond

Re: [Libusbx-devel] libusb segfaults - causes pcscd to crash

On 2012.08.02 19:30, Orin Eman wrote: > I've seen the list get screwed up by trying to reissue a transfer > before getting the callback. The list got a circular segment in > that case. Perhaps something like cancelling a transfer followed by > freeing it before getting the callbac

Re: [Libusbx-devel] libusb segfaults - causes pcscd to crash

On Thu, Aug 2, 2012 at 9:30 AM, Orin Eman wrote: > I've seen the list get screwed up by trying to reissue a transfer before > getting the callback. The list got a circular segment in that case. > Perhaps something like cancelling a transfer followed by freeing it before > getting the callback ca

Re: [Libusbx-devel] libusb segfaults - causes pcscd to crash

I've seen the list get screwed up by trying to reissue a transfer before getting the callback. The list got a circular segment in that case. Perhaps something like cancelling a transfer followed by freeing it before getting the callback causes this? I made a couple of changes to trap this - I'll

Re: [Libusbx-devel] libusb segfaults - causes pcscd to crash

On 2012.08.02 13:28, sebasti...@gmx-topmail.de wrote: > (gdb) print ((struct usbi_transfer*)0xb6600468)->list > $4 = {prev = 0x0, next = 0x0} This confirms that our list is screwed up and since we don't check for the next/prev validity, we end up with a NULL dereference (actually NULL-4), hence

Re: [Libusbx-devel] libusb segfaults - causes pcscd to crash

> On 2012.08.02 14:08, sebastiank wrote: > (gdb) print (struct usbi_transfer)0xb6600468 > Invalid cast. For the first backtrace: #0 0x00697e9b in add_to_flying_list (transfer=0xb6600468) at io.c:1185 (gdb) print ((struct usbi_transfer*)0xb6600468)->num_iso_packets $1 = 0 (gdb) print ((struct us

Re: [Libusbx-devel] libusb segfaults - causes pcscd to crash

On 2012.08.02 13:08, sebasti...@gmx-topmail.de wrote: > (gdb) print (struct usbi_transfer)0xb6600468 > Invalid cast. OK. Maybe it should have been print *(struct usbi_transfer*)0xb6600468, but if that doesn't work, don't worry. > For the first backtrace: > (gdb) x 0xb6600468 > 0xb6600468: 0x

Re: [Libusbx-devel] libusb segfaults - causes pcscd to crash

> On 2012.08.02 13:58, Pete Batard wrote: > I think 'print (struct usbi_transfer)0xb6600468' should do but if that > doesn't work, the hex dump should do just fine. (gdb) print (struct usbi_transfer)0xb6600468 Invalid cast. For the first backtrace: (gdb) x 0xb6600468 0xb6600468: 0x (

Re: [Libusbx-devel] libusb segfaults - causes pcscd to crash

On 2012.08.02 12:04, sebasti...@gmx-topmail.de wrote: > For the first backtrace: > (gdb) print &ctx->flying_transfers > $3 = (struct list_head *) 0x9088ed8 > > For the second backtrace: > (gdb) print &ctx->flying_transfers > $3 = (struct list_head *) 0x8b63ed8 Thanks. This confirms that our list

Re: [Libusbx-devel] libusb segfaults - causes pcscd to crash

Hello Pete, please see the lines below. For the first backtrace: (gdb) print &ctx->flying_transfers $3 = (struct list_head *) 0x9088ed8 For the second backtrace: (gdb) print &ctx->flying_transfers $3 = (struct list_head *) 0x8b63ed8 = Regards Sebastian =

Re: [Libusbx-devel] libusb segfaults - causes pcscd to crash

On 2012.08.02 11:34, Pete Batard wrote: > > (gdb) print ctx->flying_transfers > > $2 = {prev = 0xb660046c, next = 0xb660046c} > > Means that our circular list is pointing to itself (empty), so it all > looks like we got some list deletion between the initial list_empty() > check [1], that failed

Re: [Libusbx-devel] libusb segfaults - causes pcscd to crash

> (gdb) print ctx->flying_transfers > $2 = {prev = 0xb660046c, next = 0xb660046c} Means that our circular list is pointing to itself (empty), so it all looks like we got some list deletion between the initial list_empty() check [1], that failed (i.e. list was not empty then), and the time we

Re: [Libusbx-devel] libusb segfaults - causes pcscd to crash

For the first backtrace: (gdb) print *cur Cannot access memory at address 0xfffc (gdb) print *ctx $1 = {debug = 0, debug_fixed = 0, ctrl_pipe = {8, 9}, usb_devs = {prev = 0x9089010, next = 0x90899c0}, usb_devs_lock = {__data = {__lock = 0, __count = 0, __owner = 0, __kind = 0, __nusers = 0,

Re: [Libusbx-devel] libusb segfaults - causes pcscd to crash

2012/8/2 : > Hello Ludovic, > >> On 2012.08.02 10:19, Ludovic Rousseau wrote: >> In gdb can you display the different variables using: > > This is the output for the first backtrace I send today: > #0 0x00697e9b in add_to_flying_list (transfer=0xb6600468) at io.c:1185 > 1185io.c: Datei oder V

Re: [Libusbx-devel] libusb segfaults - causes pcscd to crash

Hello Ludovic, > On 2012.08.02 10:19, Ludovic Rousseau wrote: > In gdb can you display the different variables using: This is the output for the first backtrace I send today: #0 0x00697e9b in add_to_flying_list (transfer=0xb6600468) at io.c:1185 1185io.c: Datei oder Verzeichnis nicht gefunde

Re: [Libusbx-devel] libusb segfaults - causes pcscd to crash

2012/8/2 : >> On 2012.07.28 12:06, Ludovic Rousseau wrote: >> You would get more detailed information by rebuilding libusbx with debug >> info. > As you suggested, I compiled libusbx with debug info. Thanks. > I'd like you to have a final look at the attached backtrace and confirm > that the seg

Re: [Libusbx-devel] libusb segfaults - causes pcscd to crash

Just got another segmentation fault. The Backtrace differs from the previous one. = Regards Sebastian = gdb /usr/sbin/pcscd core GNU gdb (GDB) 7.1-ubuntu Copyright (C) 2010 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later

Re: [Libusbx-devel] libusb segfaults - causes pcscd to crash

> On 2012.07.28 12:06, Ludovic Rousseau wrote: > You would get more detailed information by rebuilding libusbx with debug > info. As you suggested, I compiled libusbx with debug info. I'd like you to have a final look at the attached backtrace and confirm that the segmentation fault is related to

Re: [Libusbx-devel] libusb segfaults - causes pcscd to crash

2012/7/29 : >> On 2012.07.28 15:51, Ludovic Rousseau wrote: >> Compiled with -g compilation argument, not with --enable-debug-log > Can you please give me some hints on how to compile libusbx with the right > compiler > options, that match with the Ubuntu directory scheme? No matter what > combi

Re: [Libusbx-devel] libusb segfaults - causes pcscd to crash

> On 2012.07.28 15:51, Ludovic Rousseau wrote: > I am a libusbx maintainer :-) Sorry, I did not want to underestimate your position in the libusbx project. > On 2012.07.28 15:51, Ludovic Rousseau wrote: > Different backtrace but they both indicate a crash in libusbx with no > (direct) relation wit

Re: [Libusbx-devel] libusb segfaults - causes pcscd to crash

2012/7/28 : > Did you have a look at the second file as well? It seems to me that there are > two different issues (different function calls). Different backtrace but they both indicate a crash in libusbx with no (direct) relation with pcsc-lite. >> On 2012.07.28 12:06, Ludovic Rousseau wrote:

Re: [Libusbx-devel] libusb segfaults - causes pcscd to crash

Did you have a look at the second file as well? It seems to me that there are two different issues (different function calls). > On 2012.07.28 12:06, Ludovic Rousseau wrote: > It looks like the thread is started by the okccid driver itlself and > not by pcscd. If the libusbx maintainers agree wit

Re: [Libusbx-devel] libusb segfaults - causes pcscd to crash

2012/7/28 : >> On 2012.07.28 11:46:37, Ludovic Rousseau wrote: >> Now you can use the core files to get the backtrace. >> >> Do: >> $ gdb -c core >> [...] >> (gdb) backtrace > > I already did the backtrace for each core dump. Please have a look at the > txt-files. Sorry. I missed these files. (

Re: [Libusbx-devel] libusb segfaults - causes pcscd to crash

> On 2012.07.28 11:46:37, Ludovic Rousseau wrote: > Now you can use the core files to get the backtrace. > > Do: > $ gdb -c core > [...] > (gdb) backtrace I already did the backtrace for each core dump. Please have a look at the txt-files. = Regards Sebastian = ---

Re: [Libusbx-devel] libusb segfaults - causes pcscd to crash

2012/7/27 : >> On 2012.07.23 16:22, sebastiank wrote: >> Well, maybe I found a solution to enable core dumps for the running pcscd >> process without the >> need of a reboot or re-login: >> >> http://superuser.com/questions/404239/setting-ulimit-on-a-running-process > The instructions provided by

Re: [Libusbx-devel] libusb segfaults - causes pcscd to crash

> On 2012.07.23 13:51, sebastiank wrote: >> On 2012.07.21 20:29, Ludovic Rousseau wrote: >> You may have to play with "ulimit -c unlimited" to allow the creation >> of a core file. > After doing some research about ulimit, I’m afraid to say that I can’t > enable the generation of core dumps. Well

Re: [Libusbx-devel] libusb segfaults - causes pcscd to crash

> On 2012.07.21 20:29, Ludovic Rousseau wrote: > Can you try to make pcscd generate a core file? Does this imply that the usbmon output is not useful and can be disabled? > You may have to play with "ulimit -c unlimited" to allow the creation > of a core file. After doing some research about uli

Re: [Libusbx-devel] libusb segfaults - causes pcscd to crash

2012/7/20 : >> If we can't see anything obvious from the log, we should probably aim at >> trying to replicate this data flow, to see if this is a data-bound >> reproducible situation, or if it's a data independent issue, such as a >> an overflow of concurrency issue. > Do you want me to send addi

Re: [Libusbx-devel] libusb segfaults - causes pcscd to crash

> On 2012.07.19 21:08, Pete Batard wrote: > I will actually take this opportunity to apologize to the list for > approving the message, before realizing it was being held due to the > size of its attachment, as it may inconvenience some. I have to apologize to the list members for not compressing

Re: [Libusbx-devel] libusb segfaults - causes pcscd to crash

On 2012.07.19 10:24, sebasti...@gmx-topmail.de wrote: > The attached log file contains the usbmon output of the last 30 seconds > before the segmentation fault happened. The logging stopped after that. Thanks. Next time, I suggest you compress the log, as it is a fairly large attachment. I wil

Re: [Libusbx-devel] libusb segfaults - causes pcscd to crash

On 2012.07.10 14:19, sebasti...@gmx-topmail.de wrote: > Setting the log level to 4 generates huge CPU load and the log file grows > very fast (200-300 Kbyte/s). Yeah, I was afraid of that. If you have a fair amount of traffic, the log will growth rate with match that. > Rotating the log does no

Re: [Libusbx-devel] libusb segfaults - causes pcscd to crash

Hello Pete, today, I was able to redirect the libusbx debug information (log level 4) to a file in the test environment: 'LIBUSB_DEBUG=4 /usr/sbin/pcscd --foreground --debug --apdu &> /var/log/pcscd.log' Setting the log level to 4 generates huge CPU load and the log file grows very fast (200-

Re: [Libusbx-devel] libusb segfaults - causes pcscd to crash

On 2012.07.09 09:48, sebasti...@gmx-topmail.de wrote: > Setting the debug level to 4 had no impact on the logging behavior of pcscd. This is unfortunate, as we are missing a lot of information with regards to what libusbx is doing if level 4/debug is not in use. Especially, we still have no idea

Re: [Libusbx-devel] libusb segfaults - causes pcscd to crash

Hi, I’ll give you a short summary, on what I did so far: - I installed the latest version of libusb-1.0-0 (libusbx 1.0.12 - debian package) - I set up rsyslog and logrotate like Pete suggested - I modified the /etc/init.d/pcscd script -> ‘export LIBUSB_DEBUG=3’ - I created the file /etc/default/p

Re: [Libusbx-devel] libusb segfaults - causes pcscd to crash

First of all, I’d like to thank you both very much for your fast response. I use pcsc in a productive environment (24/7), where contactless smardcards are used to grant access to an application. Because there are more than 25 pc-terminals involved, I’d appreciate a non disturbing and simple way

Re: [Libusbx-devel] libusb segfaults - causes pcscd to crash

2012/7/3 Pete Batard : > Provided pcscd will log stderr output from libusbx, that the volume of > USB traffic is not too prohibitive, and that you can be alerted and act > on a crash in a matter of hours, here's what I would do: > * using the 1.0.12 libusbx source tarball, configure libusbx with >

Re: [Libusbx-devel] libusb segfaults - causes pcscd to crash

2012/7/3 : > Dear maintainer, Hello, > I encountered an issue using pcsc-lite and libusb on Ubuntu 10.04 LTS. > Now and then libusb segfaults and causes pcscd to crash. > > The error occurred with libusb-1.0-0 (1.0.8), so I updated libusb-1.0-0 and > libusb-1.0-0-dev to 1.0.11 (libusbx) a few d

Re: [Libusbx-devel] libusb segfaults - causes pcscd to crash

Hi Sebastian, On 2012.07.03 15:35, sebasti...@gmx-topmail.de wrote: > I encountered an issue using pcsc-lite and libusb on Ubuntu 10.04 LTS. > Now and then libusb segfaults and causes pcscd to crash. > > The error occurred with libusb-1.0-0 (1.0.8), so I updated libusb-1.0-0 and > libusb-1.0-0-de

[Libusbx-devel] libusb segfaults - causes pcscd to crash

Dear maintainer, I encountered an issue using pcsc-lite and libusb on Ubuntu 10.04 LTS. Now and then libusb segfaults and causes pcscd to crash. The error occurred with libusb-1.0-0 (1.0.8), so I updated libusb-1.0-0 and libusb-1.0-0-dev to 1.0.11 (libusbx) a few days ago, hoping the issue was f