gphoto2 bus error
Artyom Mirgorodskiy
artyom.mirgorodsky at gmail.com
Sat Sep 28 17:44:39 UTC 2013
I try to build with gcc 4.6 - the same result :(
Artyom MirgorodskiyOn Saturday 28 September 2013 19:05:16 wrote:
> Yes. I updated and reinstall all ports before report...
> Possible clang problems...
>
> On Saturday 28 September 2013 14:19:28 Hans Petter Selasky wrote:
> > Hi,
> >
> > There has been no big changes in the FreeBSD's libusb recently. Looks like a problem in gphoto2. Did you upgrade to a newer gphoto2 version recently?
> >
> > --HPS
> >
> > -----Original message-----
> > > From:Artyom Mirgorodskiy <artyom.mirgorodsky at gmail.com <mailto:artyom.mirgorodsky at gmail.com> >
> > > Sent: Saturday 28th September 2013 1:05
> > > To: freebsd-current at freebsd.org <mailto:freebsd-current at freebsd.org>
> > > Subject: gphoto2 bus error
> > >
> > > I just update to current and get bus error when I try to run gphoto2:
> > >
> > > Starting program: /usr/local/bin/gphoto2 --shell
> > > (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[New LWP 100144]
> > > [New Thread 802806400 (LWP 100144/gphoto2)]
> > >
> > > Program received signal SIGBUS, Bus error.
> > > [Switching to Thread 802806400 (LWP 100144/gphoto2)]
> > > 0x0000000801552597 in pthread_mutex_destroy () from /lib/libthr.so.3
> > > (gdb) bt
> > > #0 0x0000000801552597 in pthread_mutex_destroy () from /lib/libthr.so.3
> > > #1 0x00000008040083cd in libusb_free_device_list () from /usr/lib/libusb.so.3
> > > #2 0x0000000803801a2a in gp_port_usb_exit (port=<value optimized out>)
> > > at libusb1.c:275
> > > #3 0x0000000801135763 in gp_port_free (port=0x80286d280) at gphoto2-port.c:124
> > > #4 0x0000000800ebc6a9 in gp_abilities_list_detect (list=0x802869080,
> > > info_list=0x802869050, l=0x8028ec000, context=0x45)
> > > at gphoto2-abilities-list.c:488
> > > #5 0x000000000040e0f7 in ?? ()
> > > #6 0x0000000000404aef in ?? ()
> > > #7 0x0000000800635000 in ?? ()
> > > #8 0x0000000000000000 in ?? ()
> > >
> > >
> >
>
>
--
Artyom Mirgorodskiy
More information about the freebsd-current
mailing list