[Digikam-users] Digikam started crashing

[David Woodfall]

On (07:33 22/08/06), Gilles Caulier <caulier.gilles at kdemail.net> put forth the proposition:
> On Monday 21 August 2006 23:24, David Woodfall wrote:
> > Using gdb supplies:
> >
> > Program received signal SIGSEGV, Segmentation fault.
> > [Switching to Thread -1258751056 (LWP 6033)]
> > 0xb61a263d in _int_malloc () from /lib/tls/libc.so.6
> >
> > This is the same for digikam and gphoto2. Any ideas?
> 
> Well, something witch common between digiKam and gphoto2 is broken in your 
> computer (a shared library certainly)...
> 
> Gilles Caulier

It turned out to be a badly formatted memory card on the camera.

Thanks for your input though.

> 
> >
> > On (19:19 21/08/06), David Woodfall <dave at unrealize.co.uk> put forth the 
> proposition:
> > > On (18:50 21/08/06), David Woodfall <dave at unrealize.co.uk> put forth the 
> proposition:
> > > > Just as the title says really. I'm using Slackware 11 rc2 with 2.6.15
> > > > kernel.
> > > >
> > > > Digikam version is 0.8.1 with kde 3.5.4 and my camera is a Fuji DX 10.
> > > > I tried compiling digikam 0.9.0 beta1 r1 but it has the same problem.
> > >
> > > I should add that I used Digikam successfully for several months and that
> > > this just happened today.
> > >
> > > > I downloaded 1 image ok but then it errored out on the 2nd. Since then
> > > > it only manages to list folders ok. As soon as it lists files it
> > > > crashes. I've also found that gphoto2 run from a term seg faults before
> > > > it finishes downloading images.
> > > >
> > > > Backtrace from kde debugger:
> > > >
> > > > (no debugging symbols found)
> > > > Using host libthread_db library "/lib/tls/libthread_db.so.1".
> > > > (no debugging symbols found)
> > > > [Thread debugging using libthread_db enabled]
> > > > [New Thread -1248422176 (LWP 1932)]
> > > > [New Thread -1257706576 (LWP 1959)]
> > > > 0xb6354379 in __lll_mutex_lock_wait () from /lib/tls/libc.so.6
> > > > #0  0xb6354379 in __lll_mutex_lock_wait () from /lib/tls/libc.so.6
> > > > #1  0xb62e5a1b in _L_mutex_lock_3089 () from /lib/tls/libc.so.6
> > > > #2  0xbfc3a870 in ?? ()
> > > > #3  0xbfc3a648 in ?? ()
> > > > #4  0xb6268cd0 in ?? () from /usr/lib/./libstdc++.so.6
> > > > #5  0x08350a38 in ?? ()
> > > > #6  0x00000000 in ?? ()
> > > > --
> > > > Have an adequate day.
> > > >
> > > > _______________________________________________
> > > > Digikam-users mailing list
> > > > Digikam-users at kde.org
> > > > https://mail.kde.org/mailman/listinfo/digikam-users
> > >
> > > --
> > > Any sufficiently advanced bug is indistinguishable from a feature.
> > > 		-- Rich Kulawiec
> > >
> > > _______________________________________________
> > > Digikam-users mailing list
> > > Digikam-users at kde.org
> > > https://mail.kde.org/mailman/listinfo/digikam-users
> _______________________________________________
> Digikam-users mailing list
> Digikam-users at kde.org
> https://mail.kde.org/mailman/listinfo/digikam-users

-- 
Why is the alphabet in that order?  Is it because of that song?