Bug 283505 - Akonadi-googledata crash on start
Summary: Akonadi-googledata crash on start
Status: RESOLVED DUPLICATE of bug 283615
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: GoogleData Resource (show other bugs)
Version: 4.7
Platform: Mageia RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Adenilson Cavalcanti
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-06 23:16 UTC by Balcaen John
Modified: 2011-10-13 17:35 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
bt of akonadi-google (69.60 KB, text/plain)
2011-10-07 09:41 UTC, Balcaen John
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Balcaen John 2011-10-06 23:16:44 UTC
Application: akonadi_googledata_resource (4.7)
KDE Platform Version: 4.7.2 (4.7.2)
Qt Version: 4.7.4
Operating System: Linux 3.0.6-desktop-1.mga2 x86_64
Distribution: "Mageia Cauldron"

-- Information about the crash:
- What I was doing when the application crashed:

Configure akonadi-googledata & let's the akonadi agent start
it's going to crash every time.
Test are done under KDE SC 4.7.2 with akonadi 1.6.2

The crash can be reproduced every time.

-- Backtrace:
Application: Akonadi Google Contacts Resource (akonadi_googledata_resource), signal: Aborted
[KCrash Handler]
#6  0x00007fa4297ffff5 in raise () from /lib64/libc.so.6
#7  0x00007fa429801786 in abort () from /lib64/libc.so.6
#8  0x00007fa429e1042d in __gnu_cxx::__verbose_terminate_handler () at ../../../../libstdc++-v3/libsupc++/vterminate.cc:93
#9  0x00007fa429e0e646 in __cxxabiv1::__terminate (handler=<value optimized out>) at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:39
#10 0x00007fa429e0e673 in std::terminate () at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:49
#11 0x00007fa429e0e7c6 in __cxxabiv1::__cxa_rethrow () at ../../../../libstdc++-v3/libsupc++/eh_throw.cc:116
#12 0x00007fa42c52a9f2 in QEventLoop::exec (this=0x7fff6ce4b960, flags=...) at kernel/qeventloop.cpp:214
#13 0x00007fa42c52edbb in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1064
#14 0x00007fa42c8ee947 in Akonadi::ResourceBase::init (r=0x1701590) at /usr/src/debug/kdepimlibs-4.7.2/akonadi/resourcebase.cpp:393
#15 0x000000000040cee8 in init<GoogleContactsResource> (argc=<value optimized out>, argv=<value optimized out>) at /usr/include/akonadi/resourcebase.h:188
#16 main (argc=<value optimized out>, argv=<value optimized out>) at /usr/src/debug/akonadi-googledata-1.2.0/contacts/googledataresource.cpp:1546

Possible duplicates by query: bug 283436, bug 283432, bug 282877, bug 281088, bug 277968.

Reported using DrKonqi
Comment 1 Christophe Marin 2011-10-07 08:24:21 UTC
John, we didn't see any fix from the maintainer during the last two years. It may be wise to offer the akonadi-google resource to your distribution instead (despite being quite recent, it was reported to work much better already)

As for this crash, in its current state it doesn't help. You can try to run the resource in gdb and set a catchpoint to get a useful backtrace

(either using 'catch throw' or adding a breakpoint to _cxa_rethrow)
Comment 2 Balcaen John 2011-10-07 09:17:27 UTC
ok, in fact i have the same crash with akonadi-google (with the last git) so i'll report the one i have one for akonadi-google but i'll try to get a more detailled gdb since it's « quite similar » to this one (& so probably not useful at all :/ )
Comment 3 Balcaen John 2011-10-07 09:41:59 UTC
Created attachment 64305 [details]
bt of akonadi-google

Ok i'm attaching here the akonadi-google crash (because this bug is already report & from the « small bt i get from Dr Konqui it seems similar in most part of the akonadi-googledata crash )
I did attached gdb via a gdb --pid to the /usr/bin/akonadi_googlecontacts_resource & use the catch throw command in gdb (i'm not really used to gdb so maybe there's something more to do)
i also put the bt full result in case of.
Is there anyway to get a more useful bt ? (i think only about attaching to the pid via a gdb --pid but i'm might be wrong)


Regards
Comment 4 Christophe Marin 2011-10-13 17:35:47 UTC
Thanks.

*** This bug has been marked as a duplicate of bug 283615 ***