Date: Sat, 08 Mar 2008 14:58:08 +0000 From: Mark Ovens <parish@magichamster.com> To: freebsd-ports@freebsd.org Cc: Vladimir Kushnir <vkushnir@bigmir.net> Subject: Re: 7.0-RELEASE: digikam 0.9.3 dumps core on startup Message-ID: <47D2A980.9030100@magichamster.com> In-Reply-To: <20080307204933.N35653@kushnir1.kiev.ua> References: <47D032ED.1040805@magichamster.com> <20080307001327.P65422@kushnir1.kiev.ua> <3649.213.1.249.253.1204887329.squirrel@postbag.localdomain> <20080307204933.N35653@kushnir1.kiev.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
Vladimir Kushnir wrote:
>
> Hmm... No, this never happened here. Everything works perfectly all
> right. My sqlite3 compiled with threads though, could it be that?
>
>>
>> I also had problems with the system gdb core dumping in 6.3 - this still
>> happens in 7.0 does it?
>>
>
> Probably. It does here under -CURRENT, anyway :-(
>
I built a debug version of digikam and started it from gdb (which isn't
crashing on my 7.0 system :-) ).
When digikam hung this is the stack trace:
/home/mark{21}% gdb /usr/local/bin/digikam
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-marcel-freebsd"...
(gdb) run
Starting program: /usr/local/bin/digikam
[New LWP 100190]
[New Thread 0x2a801100 (LWP 100190)]
[New Thread 0x2a801f00 (LWP 100230)]
[Thread 0x2a801f00 (LWP 100230) exited]
[New Thread 0x2a802300 (LWP 100231)]
[Thread 0x2a802300 (LWP 100231) exited]
digikam: ScanLib: Finding non-existing Albums: 48 ms
digikam: ScanLib: Finding items not in the database or disk: 1351 ms
digikam: ScanLib: Updating items without date: 22 ms
Found dcraw version: 8.81
^C
Program received signal SIGINT, Interrupt.
[Switching to Thread 0x2a801100 (LWP 100190)]
0x2a5543b1 in write () from /lib/libc.so.7
(gdb) bt
#0 0x2a5543b1 in write () from /lib/libc.so.7
#1 0x2a4701f2 in write () from /lib/libthr.so.3
#2 0x2a171aca in ?? () from /usr/local/lib/libfam.so.0
#3 0x2a174e78 in FAMMonitorCollection () from /usr/local/lib/libfam.so.0
#4 0x291c0bc9 in KDirWatchPrivate::useFAM () from
/usr/local/lib/libkio.so.6
#5 0x291c14ff in KDirWatchPrivate::addEntry () from
/usr/local/lib/libkio.so.6
#6 0x291c1a0f in KDirWatch::addDir () from /usr/local/lib/libkio.so.6
#7 0x28222684 in Digikam::AlbumManager::scanPAlbums (this=0x2a8a1670)
at albummanager.cpp:443
#8 0x28222d4d in Digikam::AlbumManager::refresh (this=0x2a8a1670)
at albummanager.cpp:337
#9 0x2822306f in Digikam::AlbumManager::startScan (this=0x2a8a1670)
at albummanager.cpp:330
#10 0x281e530d in DigikamApp (this=0x2a899180) at digikamapp.cpp:165
#11 0x0804aff7 in main (argc=676267148, argv=0x2a8cc122) at main.cpp:309
(gdb)
It seems that the problem maybe connected with fam. digikam seems to use
gamin by default (at least that's what the packages are built with) but
I have this in /etc/make.conf:
WITH_FAM_SYSTEM=fam
so fam is used instead. Could this be where the problem is?
Thanks for your help.
Regards,
Mark
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?47D2A980.9030100>