On Sun, Nov 27, 2011 at 11:41:08PM +0100, Achim Schaefer wrote: > On 11/27/2011 08:06 PM, Guido Günther wrote: > >So it'd be good to know how args looks like. The code in libudev is: > > > > udev_device_set_syspath(udev_device, path); > I added a printf here: > printf("devpath: %s(orig) %s (from dev)\n", path, > udev_device_get_devpath(udev_device)); > > > info(udev, "device %p has devpath '%s'\n", udev_device, > > udev_device_get_devpath(udev_device)); > > > >So either udev_device or udev_device_get_devpath(udev_device) are > >possibly bogus. Since udev_device comes freshly from udev_device_new > >that's an unlikely candidate. You can either use gdb or some printf in > >libudev to track that. > > > >That said you could also try to run libvirt under valgrind which might > >point you to the offending part. > > > And using valgrind I now get: > devpath: /sys/devices/virtual/block/md2(orig) > /devices/virtual/block/md2 (from dev) > 2011-11-27 23:34:27.920: 23929: error : > udev_device_new_from_syspath:719 : device 0x13f9b238 has devpath > 'pJ�'
This looks like an issue in libudev. I'm cc'ing the udev maintainers, maybe they have an idea. The backtrace is here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=649435#17 Cheers, -- Guido -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org