From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-dev/2012-November/020388.html | 89 ++++++++++++++++++++++++++++ 1 file changed, 89 insertions(+) create mode 100644 zarb-ml/mageia-dev/2012-November/020388.html (limited to 'zarb-ml/mageia-dev/2012-November/020388.html') diff --git a/zarb-ml/mageia-dev/2012-November/020388.html b/zarb-ml/mageia-dev/2012-November/020388.html new file mode 100644 index 000000000..eea3a308d --- /dev/null +++ b/zarb-ml/mageia-dev/2012-November/020388.html @@ -0,0 +1,89 @@ + + + + [Mageia-dev] Evolution segfaults when trying to confirm a calendar invite + + + + + + + + + +

[Mageia-dev] Evolution segfaults when trying to confirm a calendar invite

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Wed Nov 28 20:40:38 CET 2012 +

+
+ +
On 28 November 2012 17:23, Colin Guthrie <mageia at colin.guthr.ie> wrote:
+>> I have the same feeling with regardds to my computers.
+>> What I do in these situations is to install the debug packages, run the application in gdb, record the debug info, and then uninstall the debug packages.
+>>
+>> You don't have to keep the debug packages installed after you've collected the debug info.
+>
+> Longer term it would be nice to be able to have a service to upload the
+> core files and then generate the backtrace remotely.
+
+libreport and the associated packages do that...
+But that's less needed now that we have minidebug info.
+
+What's more, even without debug packages, gdb will got a useful backtrace
+
+ + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ -- cgit v1.2.1