Hi Ludovic,
thanks for your response.
On Wed, Mar 23, 2011 at 02:18:46PM +0100, Ludovic Rousseau wrote:
> Can you rebuild pcscd in debug mode and run it inside gdb to get a
> backtrace?
I already did that and I already sent another message to this bug indicating
where exactly it crashes and why...
There is nothing 'unusual' in the backtrace, it really just is that:
In function HPRescanUsbBus():
parent = udev_device_get_devnode(parent);
udev_device_get_devnode() returns NULL (which is possible, according to
http://www.kernel.org/pub/linux/utils/kernel/hotplug/libudev/libudev-udev-device.html#udev-device-get-devnode),
but pcscd uses this result unverified later in a strdup().
> Since only pcscd is involved you can run it directly from the source
> directory within installing it.
yes, that's what I did.
--
- Harald Welte <lafo...@gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
