thanks, commited to openct trunk.
Regards, Andreas
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel
Am Dienstag 03 November 2009 13:41:07 schrieb Viktor TARASOV:
> Hi,
>
> I would like to update the support of the Oberthur card
> and to implement the PIN unblocking style of the Oberthur's native
> middleware.
>
> For the Oberthur card a PIN is some internal object (it's not like a SDO
> object)
hmm, debugging is a problem in opensc code. here are my ideas.
I haven't figured out how to ltrace opensc, mostly when it used via opensc-
pkcs11.so. so what can I do to find a bug?
a) gdb and single step, taking notes till I find out how opensc works in
some area and get a clue where the bug i
Viktor TARASOV wrote:
> In a fact, I was looking through libopensc/pkcs.c (ex. +365, +525, ..) .
>
Sorry, should be read as
In a fact, I was looking through libopensc/pkcs15.c (ex. +365, +525, ..) .
Regards,
Viktor Tarasov.
>
>> ___
>
Aleksey Samsonov wrote:
> Viktor TARASOV wrote:
>
>> my general question is:
>> will you agree to have a little bit more of the debug messages in the
>> common sources ?
>> IMHO, it will facilitate the debugging and the comprehension of the 'how
>> it works'.
>>
>
> If it is useful, yes.
Aleksey Samsonov wrote:
>> Does it exists any rule for the assigning of the debug level for debug
>> messages ?
>
> I think we have to follow common sence.
>
Also you can find some information here
http://www.opensc-project.org/pipermail/opensc-devel/2009-September/012466.html
Hello,
Viktor TARASOV wrote:
> Hi,
>
> my general question is:
> will you agree to have a little bit more of the debug messages in the
> common sources ?
> IMHO, it will facilitate the debugging and the comprehension of the 'how
> it works'.
If it is useful, yes.
> I mean, at least, to use m
Hi,
my general question is:
will you agree to have a little bit more of the debug messages in the
common sources ?
IMHO, it will facilitate the debugging and the comprehension of the 'how
it works'.
I mean, at least, to use more of the log macros ( SC_FUNC_RETURN,
SC_FUNC_CALLED and SC_TEST_RE
