registry team mailing list archive

[Barry Flanagan <barry@xxxxxxxxxxx>]

Seems to have fixed the issue on my MB 5,1 running Lucid as well.

-Barry Flanagan



On 9 June 2010 22:42, Olivier Grisel <olivier.grisel@xxxxxxxxx> wrote:
> @Eric: same for me on a MacBook Pro 5,5 running lucid. I can now suspend
> and resume without having libusb segfault in the process. Thanks!
>
> --
> usb_find_devices() crashed with SIGSEGV in free()
> https://bugs.launchpad.net/bugs/427805
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
> Status in libusb: New
> Status in “libusb” package in Ubuntu: In Progress
>
> Bug description:
> Binary package hint: devicekit-power
>
> rolando@defiant:~$ lsb_release -rd
> Description:    Ubuntu karmic (development branch)
> Release:        9.10
>
> Hi, I only turn on my computer and then i saw the bug
>
> ProblemType: Crash
> Architecture: amd64
> Date: Thu Sep 10 04:39:51 2009
> DistroRelease: Ubuntu 9.10
> ExecutablePath: /usr/lib/devicekit-power/devkit-power-daemon
> NonfreeKernelModules: wl nvidia
> Package: devicekit-power 010-0ubuntu1
> ProcCmdline: /usr/lib/devicekit-power/devkit-power-daemon
> ProcEnviron:
>
> ProcVersionSignature: Ubuntu 2.6.31-10.30-generic
> SegvAnalysis:
>  Segfault happened at: 0x7f8ac7ddf629 <free+25>:        mov    -0x8(%rdi),%rax
>  PC (0x7f8ac7ddf629) ok
>  source "-0x8(%rdi)" (0x-0000007) not located in a known VMA region (needed readable region)!
>  destination "%rax" ok
> SegvReason: reading NULL VMA
> Signal: 11
> SourcePackage: devicekit-power
> StacktraceTop:
>  free () from /lib/libc.so.6
>  usb_destroy_configuration ()
>  usb_free_dev () from /lib/libusb-0.1.so.4
>  usb_find_devices () from /lib/libusb-0.1.so.4
>  ?? ()
> Title: devkit-power-daemon crashed with SIGSEGV in free()
> Uname: Linux 2.6.31-10-generic x86_64
> UserGroups:
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/libusb/+bug/427805/+subscribe
>

-- 
usb_find_devices() crashed with SIGSEGV in free()
https://bugs.launchpad.net/bugs/427805
You received this bug notification because you are a member of Registry
Administrators, which is the registrant for libusb.