Hello, On Sun, Jan 15, 2012 at 12:33 PM, Ludovic Rousseau <ludovic.rouss...@gmail.com> wrote: > Le 14/01/12 20:12, Dmitry Eremin-Solenikov a écrit : >> >> Hello, > > > Hello, > >> Could you please add a package with debugging symbols. Please consider >> the attached patch (used locally). > > > Why do you need the debugging symbols? Do you want to debug libpcsclite > itself? > > Why can't you debug the application using PC/SC if you do not have the > debugging symbols of libpcsclite? > > I am not against the idea. I just want to understand why it is needed.
Well, of course I can debug my application. However with pcsclite symbols I get traces with more information. Compare (parts of valgrind output): --- Without libpcsclite-dbg --- ==18964== Syscall param socketcall.send(msg) points to uninitialised byte(s) ==18964== at 0x411BFC1: send (socket.S:64) ==18964== by 0x4048E50: ??? (in /usr/lib/libpcsclite.so.1.0.0) ==18964== by 0x4048FE4: ??? (in /usr/lib/libpcsclite.so.1.0.0) ==18964== by 0x404469C: SCardConnect (in /usr/lib/libpcsclite.so.1.0.0) ==18964== by 0x80491A7: scard_connect (scard.c:88) ==18964== by 0x4064E45: (below main) (libc-start.c:228) --- End of trace--- --- With libpcsclite-dbg --- ==18362== Syscall param socketcall.send(msg) points to uninitialised byte(s) ==18362== at 0x411BFC1: send (socket.S:64) ==18362== by 0x4048E50: MessageSend (winscard_msg.c:355) ==18362== by 0x4048FE4: MessageSendWithHeader (winscard_msg.c:294) ==18362== by 0x404469C: SCardConnect (winscard_clnt.c:825) ==18362== by 0x80491A7: scard_connect (scard.c:88) ==18362== by 0x4064E45: (below main) (libc-start.c:228) ==18362== Address 0xbef962b3 is on thread 1's stack --- End of trace --- -- With best wishes Dmitry -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
