5 Dec
2014
5 Dec
'14
7:57 p.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA224
On Friday 05 December 2014 20:32:45 Timothy Pearson
wrote:
--signal
ok, here is another dump:
https://paste.kde.org/pvrbpvonl
maybe this is more useful ?
Werner
Yes, it is more useful--at least this one correctly identified the origin
of the crash.
Can you file a bug report on this? I am likely to lose track of it
otherwise, and doing so will allow other developers to pick it up if they
can get to it before I have time.
Tim
On Friday
05 December 2014 16:18:24 Timothy Pearson wrote:
> > On Friday 05 December 2014 14:36:43 Timothy Pearson wrote:
> >> > On Thursday 04 December 2014 15:15:31 Timothy Pearson wrote:
> >> >> > - konact works, but crashes reproducable upon exit.
> >> >>
> >> >> Forgot to address this. Have you sent in a backtrace (after
> >>
> >> installing
> >>
> >> >> tdepim-trinity-dbg) of the crash? Using the "Report
Crash"
button
>
> is
>
> >> >> preferred as I will get a properly formatted dump.
> >> >
> >> > ok, the crash report is here:
> >> > https://paste.kde.org/pzbyjlkfa
> >> > hope it helps (done after installing tdepim debug package)
> >> >
> >> > Werner
> >>
> >> Did DrKonqui not work?
> >
> > no, unfortunately not, it is installed, though.
> >
> >> DrKonqi generates additional helpful information
> >> vs. a straight gdb 'bt', especially with multithreaded programs
such
>
> as
>
> >> the tdepim suite.
> >
> > is there a way to trigger drkonqi start when a crash happens ?
>
> It *should* be automatic; I've never seen a case where DrKonqui does
not
> pop up when a program crashes--provided
DrKonqui is actually
installed
> and
> you are running programs from within a TDE desktop session.
>
> If DrKonqui is not popping up, and since you were able to get a
> backtrace,
> then I presume you are running akregator from within gdb? Try
running
it
outside of gdb to see if you get the DrKonqui crash popup.
sorry, Tim,
I provided wrong information - it was indeed drkonqi where I got the
mentioned report from :
3652 ? S 0:00 drkonqi -display :0 --appname kontact 11 --pid 3456 --appversion 1.2.9 (enterprise35
0.20100827.1168748)
--programname
Kontact --bugaddress http://bugs.trinitydesktop.org --startupid
debian;1417804842;441769;3412_TIME55532
(I just presumed there must be some drkonqi caption or thelike in the
crash popup window...)
Werner
And it was my fault for not reading to the end of the provided file. I
assumed since the crash was not sent in to the TDE dump server that you
had just attached GDB to the process...
In any case it still doesn't look like I can glean much from the dump as
the trace is shortened by the possibly corrupted stack. -----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iFYEARELAAYFAlSCDg8ACgkQLaxZSoRZrGG2qQDbBzGWFh5cl19Cr94IqVd+AbFM
IOQilBDhtL3SvQDfaBfEDeY/h6dAjoBbQfa/ytKbTSjTKlNuth7cHg==
=S97f
-----END PGP SIGNATURE-----