30 Apr
2011
30 Apr
'11
10:10 p.m.
What is the best way to troubleshoot run-time crashes?
Do the packages have to be built a certain way?
I've read about backtraces, core dumps, and using gdb. I'm no programmer, so what
is the best way for me to troublesoot?
In particular, I am running KDE 3.5.10, recompiled for Slackware 13.1. KMail always now
crashes whenever I try to do anything with the composer window (save as draft, send,
etc.). Boom. Just disappears. Almost as if I had started KMail with the --compose option.
The app disappears and I have to restart KMail. The funny thing is the message gets stored
in the Outbox.
I want to troubleshoot in case this bug carries over to Trinity.
Thanks.
Darrell
1 May
1 May
2:28 a.m.
New subject: [trinity-devel] Troubleshooting Run Time Crashes
Le Sat, 30 Apr 2011 15:10:48 -0700 (PDT),
Darrell Anderson <humanreadable(a)yahoo.com> a écrit :
What is the best way to troubleshoot run-time
crashes?
Do the packages have to be built a certain way?
You have to build kdepim (no need,
at least for now, to recompile other
packages) including "-g" in your CFLAGS and CXXFLAGS in order to have
a useful backtrace.
I've read about backtraces, core dumps, and using gdb. I'm no
programmer, so what is the best way for me to troublesoot?
$ gdb
(gdb) file /usr/bin/kmail
(gdb) run
<trigger the crash>
(gdb) bt
<you obtain the backtrace>
I don't know if this will be enough, but I'm not an expert debugger :).
In particular, I am running KDE 3.5.10, recompiled for Slackware
13.1. KMail always now crashes whenever I try to do anything with the
composer window (save as draft, send, etc.). Boom. Just disappears.
Almost as if I had started KMail with the --compose option. The app
disappears and I have to restart KMail. The funny thing is the
message gets stored in the Outbox.
I want to troubleshoot in case this bug carries over to Trinity.
Thanks.
Darrell
---------------------------------------------------------------------
To unsubscribe, e-mail:
trinity-devel-unsubscribe(a)lists.pearsoncomputing.net For additional
commands, e-mail: trinity-devel-help(a)lists.pearsoncomputing.net Read
list messsages on the Web archive:
http://trinity-devel.pearsoncomputing.net/ Please remember not to
top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
2 May
2 May
4:12 p.m.
New subject: [trinity-devel] Troubleshooting Run Time Crashes
I've read
about backtraces, core dumps, and using gdb.
I'm no
programmer, so what is the best way for me to
troublesoot?
$ gdb
(gdb) file /usr/bin/kmail
(gdb) run
<trigger the crash>
(gdb) bt
<you obtain the backtrace>
I don't know if this will be enough, but I'm not an expert
debugger :). 
4:52 p.m.
New subject: [trinity-devel] Troubleshooting Run Time Crashes
I've read about backtraces, core dumps, and using
gdb.
I'm no
programmer, so what is the best way for me to
troublesoot?
$ gdb
(gdb) file /usr/bin/kmail
(gdb) run
<trigger the crash>
(gdb) bt
<you obtain the backtrace>
I don't know if this will be enough, but I'm not an expert
debugger :).
10:46 p.m.
New subject: [trinity-devel] Troubleshooting Run Time Crashes
I gave that a
go. gdb reported that kmail exited
normally. With some trial
and error testing, I copied /usr/bin/kmail and
/usr/lib/libkmailprivate.so
from my Slackware 12.2 package and then the
problem
disappeared. At this
point I can only guess that something in the
kmail
composer code does not
compile correctly and instead causes the entire
app to
close rather than
just the composer window.
Darrell
You may need to try something like this:
gdb --arg kmail --nofork
kmail is just a kdeinit executable that will normally exit
as soon as the
GUI is loaded unless forced not to.
11 p.m.
New subject: [trinity-devel] Troubleshooting Run Time Crashes
I gave that a go. gdb reported that kmail exited
normally. With some trial
and error testing, I copied /usr/bin/kmail and
/usr/lib/libkmailprivate.so
from my Slackware 12.2 package and then the
problem
disappeared. At this
point I can only guess that something in the
kmail
composer code does not
compile correctly and instead causes the entire
app to
close rather than
just the composer window.
Darrell
You may need to try something like this:
gdb --arg kmail --nofork
kmail is just a kdeinit executable that will normally exit
as soon as the
GUI is loaded unless forced not to.
11:54 p.m.
New subject: [trinity-devel] Troubleshooting Run Time Crashes
With your
suggestion I received something meaningful:
Program received signal SIGSEGV, Segmentation fault.
0xb6491dc3 in DCOPObject::~DCOPObject() () from
/usr/lib/libDCOP.so.4
libDCOP.so.4 is a sym link to libDCOP.so.4.2.0, which
is installed by the
kdelibs package.
What do I try next?
Install the debugging packages and get me a backtrace. :-)
3 May
3 May
6:01 p.m.
New subject: [trinity-devel] Troubleshooting Run Time Crashes
Install the debugging packages and get me a backtrace.
:-)
Okay, I finally got that figured out. Here is the backtrace:
================================
#0 0xb623627b in DCOPObject::~DCOPObject() () from /usr/lib/libDCOP.so.4
#1 0xb7c8111e in KMComposeWin::~KMComposeWin() () from /usr/lib/libkmailprivate.so
#2 0xb5cf91a0 in QObject::event(QEvent*) () from /usr/lib/qt-3.3.8b/lib/libqt-mt.so.3
#3 0xb5d331cc in QWidget::event(QEvent*) () from /usr/lib/qt-3.3.8b/lib/libqt-mt.so.3
#4 0xb5df3f42 in QMainWindow::event(QEvent*) () from
/usr/lib/qt-3.3.8b/lib/libqt-mt.so.3
#5 0xb7c7fea9 in KMComposeWin::event(QEvent*) () from /usr/lib/libkmailprivate.so
#6 0xb5c94b47 in QApplication::internalNotify(QObject*, QEvent*) () from
/usr/lib/qt-3.3.8b/lib/libqt-mt.so.3
#7 0xb5c95e2b in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/qt-3.3.8b/lib/libqt-mt.so.3
#8 0xb634ff25 in KApplication::notify(QObject*, QEvent*) () from
/usr/lib/libkdecore.so.4
#9 0xb5c9695c in QApplication::sendPostedEvents(QObject*, int) () from
/usr/lib/qt-3.3.8b/lib/libqt-mt.so.3
#10 0xb5c96ae6 in QApplication::sendPostedEvents() () from
/usr/lib/qt-3.3.8b/lib/libqt-mt.so.3
#11 0xb5c40c35 in QEventLoop::processEvents(unsigned int) () from
/usr/lib/qt-3.3.8b/lib/libqt-mt.so.3
#12 0xb5cad7c0 in QEventLoop::enterLoop() () from /usr/lib/qt-3.3.8b/lib/libqt-mt.so.3
#13 0xb5cad666 in QEventLoop::exec() () from /usr/lib/qt-3.3.8b/lib/libqt-mt.so.3
#14 0xb5c9519f in QApplication::exec() () from /usr/lib/qt-3.3.8b/lib/libqt-mt.so.3
#15 0x0804a988 in ?? ()
#16 0xb533fb86 in __libc_start_main () from /lib/libc.so.6
#17 0x0804a781 in ?? ()
================================
What I did:
Start KMail.
Open the Compose window.
Select the Close widget [X] in the Compose window.
On my system: /lib/libc.so.6 -> libc-2.11.1.so, which is installed by glibc 2.11.1.
Any ideas?
Darrell
11:23 p.m.
New subject: [trinity-devel] Troubleshooting Run Time Crashes (KMail/Compose)
Okay, I finally got that figured out. Here is the
backtrace:
================================
#0 0xb623627b in DCOPObject::~DCOPObject() () from
/usr/lib/libDCOP.so.4
#1 0xb7c8111e in KMComposeWin::~KMComposeWin() ()
from /usr/lib/libkmailprivate.so
#2 0xb5cf91a0 in QObject::event(QEvent*) () from
/usr/lib/qt-3.3.8b/lib/libqt-mt.so.3
#3 0xb5d331cc in QWidget::event(QEvent*) () from
/usr/lib/qt-3.3.8b/lib/libqt-mt.so.3
#4 0xb5df3f42 in QMainWindow::event(QEvent*) () from
/usr/lib/qt-3.3.8b/lib/libqt-mt.so.3
#5 0xb7c7fea9 in KMComposeWin::event(QEvent*) () from
/usr/lib/libkmailprivate.so
#6 0xb5c94b47 in
QApplication::internalNotify(QObject*, QEvent*) () from
/usr/lib/qt-3.3.8b/lib/libqt-mt.so.3
#7 0xb5c95e2b in QApplication::notify(QObject*,
QEvent*) () from /usr/lib/qt-3.3.8b/lib/libqt-mt.so.3
#8 0xb634ff25 in KApplication::notify(QObject*,
QEvent*) () from /usr/lib/libkdecore.so.4
#9 0xb5c9695c in
QApplication::sendPostedEvents(QObject*, int) () from
/usr/lib/qt-3.3.8b/lib/libqt-mt.so.3
#10 0xb5c96ae6 in QApplication::sendPostedEvents() () from
/usr/lib/qt-3.3.8b/lib/libqt-mt.so.3
#11 0xb5c40c35 in QEventLoop::processEvents(unsigned int)
() from /usr/lib/qt-3.3.8b/lib/libqt-mt.so.3
#12 0xb5cad7c0 in QEventLoop::enterLoop() () from
/usr/lib/qt-3.3.8b/lib/libqt-mt.so.3
#13 0xb5cad666 in QEventLoop::exec() () from
/usr/lib/qt-3.3.8b/lib/libqt-mt.so.3
#14 0xb5c9519f in QApplication::exec() () from
/usr/lib/qt-3.3.8b/lib/libqt-mt.so.3
#15 0x0804a988 in ?? ()
#16 0xb533fb86 in __libc_start_main () from /lib/libc.so.6
#17 0x0804a781 in ?? ()
================================
What I did:
Start KMail.
Open the Compose window.
Select the Close widget [X] in the Compose window.
On my system: /lib/libc.so.6 -> libc-2.11.1.so, which is
installed by glibc 2.11.1.
Any ideas?
Darrell
Interestingly, I can copy /usr/bin/kmail and /usr/lib/libkmailprivate.so compiled under
Slackware 12.2 and not experience the crash when closing the Compose window.
Darrell
4 May
4 May
8:13 p.m.
New subject: [trinity-devel] Troubleshooting Run Time Crashes (KMail/Compose)
theres a issue around glibc 2.1X under virtual machines, are running kmail
in virtual machine?
also are other issues about glibc 2.10 in trinity project, currenly hard to
solved!
On Tue, May 3, 2011 at 6:53 PM, Darrell Anderson <humanreadable(a)yahoo.com>wrote;wrote:
--
Lenz McKAY Gerardo (PICCORO)
http://qgqlochekone.blogspot.com
Cofundador de Venenux; debian based multimedia alike free only zealots
users (oh well, i try but..too many free guidelines buahhh)
http://shutendouji.net
creador de massenkoh linux; debian enhanchements for better up to date
support on stable brand, including non-free soft.
Okay, I
finally got that figured out. Here is the
backtrace:
================================
#0 0xb623627b in DCOPObject::~DCOPObject() () from
/usr/lib/libDCOP.so.4
#1 0xb7c8111e in KMComposeWin::~KMComposeWin() ()
from /usr/lib/libkmailprivate.so
#2 0xb5cf91a0 in QObject::event(QEvent*) () from
/usr/lib/qt-3.3.8b/lib/libqt-mt.so.3
#3 0xb5d331cc in QWidget::event(QEvent*) () from
/usr/lib/qt-3.3.8b/lib/libqt-mt.so.3
#4 0xb5df3f42 in QMainWindow::event(QEvent*) () from
/usr/lib/qt-3.3.8b/lib/libqt-mt.so.3
#5 0xb7c7fea9 in KMComposeWin::event(QEvent*) () from
/usr/lib/libkmailprivate.so
#6 0xb5c94b47 in
QApplication::internalNotify(QObject*, QEvent*) () from
/usr/lib/qt-3.3.8b/lib/libqt-mt.so.3
#7 0xb5c95e2b in QApplication::notify(QObject*,
QEvent*) () from /usr/lib/qt-3.3.8b/lib/libqt-mt.so.3
#8 0xb634ff25 in KApplication::notify(QObject*,
QEvent*) () from /usr/lib/libkdecore.so.4
#9 0xb5c9695c in
QApplication::sendPostedEvents(QObject*, int) () from
/usr/lib/qt-3.3.8b/lib/libqt-mt.so.3
#10 0xb5c96ae6 in QApplication::sendPostedEvents() () from
/usr/lib/qt-3.3.8b/lib/libqt-mt.so.3
#11 0xb5c40c35 in QEventLoop::processEvents(unsigned int)
() from /usr/lib/qt-3.3.8b/lib/libqt-mt.so.3
#12 0xb5cad7c0 in QEventLoop::enterLoop() () from
/usr/lib/qt-3.3.8b/lib/libqt-mt.so.3
#13 0xb5cad666 in QEventLoop::exec() () from
/usr/lib/qt-3.3.8b/lib/libqt-mt.so.3
#14 0xb5c9519f in QApplication::exec() () from
/usr/lib/qt-3.3.8b/lib/libqt-mt.so.3
#15 0x0804a988 in ?? ()
#16 0xb533fb86 in __libc_start_main () from /lib/libc.so.6
#17 0x0804a781 in ?? ()
================================
What I did:
Start KMail.
Open the Compose window.
Select the Close widget [X] in the Compose window.
On my system: /lib/libc.so.6 -> libc-2.11.1.so, which is
installed by glibc 2.11.1.
Any ideas?
Darrell
Interestingly, I can copy /usr/bin/kmail and /usr/lib/libkmailprivate.so
compiled under Slackware 12.2 and not experience the crash when closing the
Compose window.
Darrell
---------------------------------------------------------------------
To unsubscribe, e-mail:
trinity-devel-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail:
trinity-devel-help(a)lists.pearsoncomputing.net
Read list messsages on the Web archive:
http://trinity-devel.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
8:34 p.m.
New subject: [trinity-devel] Troubleshooting Run Time Crashes (KMail/Compose)
From: PICCORO McKAY Lenz
<mckaygerhard(a)gmail.com>
Subject: Re: [trinity-devel] Troubleshooting Run Time Crashes (KMail/Compose)
To: trinity-devel(a)lists.pearsoncomputing.net
Date: Wednesday, May 4, 2011, 3:13 PM
theres a issue around glibc 2.1X under
virtual machines, are running kmail in virtual
machine?
also are other issues about glibc 2.10 in
trinity project, currenly hard to solved!
I'm not running in a virtual machine.
I notice only two glibc patches in the svn commits. This glitch with the Compose window is
the only one I have discovered.
Darrell
8:35 p.m.
New subject: [trinity-devel] Troubleshooting Run Time Crashes (KMail/Compose)
On Wed, May 4, 2011 at 16:13, PICCORO McKAY Lenz <mckaygerhard(a)gmail.com> wrote:
theres a issue around glibc 2.1X under virtual
machines, are running kmail
in virtual machine?
where is this from? do you have a link to a bug?
--
later, Robert Xu
9:01 p.m.
New subject: [trinity-devel] Troubleshooting Run Time Crashes (KMail/Compose)
theres a around bug time error some time ago..
in "[trinity-devel] Troubleshooting Run Time Crashes" mail thread and also
"[trinity-devel] New Qt3 xsession crash on x86_64 - need collective wisdom
:" and also
In all common denominator is glibc under virtualmachine on/or 64bit, almost
always accompanied by xcb crash issues.
theres more info about glibc changes and issues, theres a related topic in
glibc bugtraker, that can be help:
http://sources.redhat.com/bugzilla/show_bug.cgi?id=12432
On Wed, May 4, 2011 at 4:05 PM, Robert Xu <robxu9(a)gmail.com> wrote:
On Wed, May 4, 2011 at 16:13, PICCORO McKAY Lenz
<mckaygerhard(a)gmail.com>
wrote:
--
Lenz McKAY Gerardo (PICCORO)
http://qgqlochekone.blogspot.com
Cofundador de Venenux; debian based multimedia alike free only zealots
users (oh well, i try but..too many free guidelines buahhh)
http://shutendouji.net
creador de massenkoh linux; debian enhanchements for better up to date
support on stable brand, including non-free soft.
theres a issue around glibc 2.1X under virtual
machines, are running
kmail
in virtual machine?
where is this from? do you have a link to a bug?
--
later, Robert Xu
---------------------------------------------------------------------
To unsubscribe, e-mail:
trinity-devel-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail:
trinity-devel-help(a)lists.pearsoncomputing.net
Read list messsages on the Web archive:
http://trinity-devel.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
9:08 p.m.
New subject: [trinity-devel] Troubleshooting Run Time Crashes (KMail/Compose)
On Wed, May 4, 2011 at 17:01, PICCORO McKAY Lenz <mckaygerhard(a)gmail.com> wrote:
In all common denominator is glibc under
virtualmachine on/or 64bit, almost
IIRC, it was not always a VM.
always accompanied by xcb crash issues.
theres more info about glibc changes and issues, theres a related topic
in glibc bugtraker, that can be help:
http://sources.redhat.com/bugzilla/show_bug.cgi?id=12432
SRHBZ #12432 does not seem to happen in a VM, but still seems to
exhibit a bad backtrace, so I see.
--
later, Robert Xu
9:30 p.m.
New subject: [trinity-devel] Troubleshooting Run Time Crashes (KMail/Compose)
yes
xcb or glibc, In any way/case, tim said its a difficult issue to handle, my
knowledge is not enough to help for this glibc/xcb all of us .. sorry ..
On Wed, May 4, 2011 at 4:38 PM, Robert Xu <robxu9(a)gmail.com> wrote:
On Wed, May 4, 2011 at 17:01, PICCORO McKAY Lenz
<mckaygerhard(a)gmail.com>
wrote:
--
Lenz McKAY Gerardo (PICCORO)
http://qgqlochekone.blogspot.com
Cofundador de Venenux; debian based multimedia alike free only zealots
users (oh well, i try but..too many free guidelines buahhh)
http://shutendouji.net
creador de massenkoh linux; debian enhanchements for better up to date
support on stable brand, including non-free soft.
In all common denominator is glibc under
virtualmachine on/or
64bit, almost
IIRC, it was not always a VM.
always accompanied by xcb crash issues.
theres more info about glibc changes and issues, theres a related topic
in glibc bugtraker, that can be help:
http://sources.redhat.com/bugzilla/show_bug.cgi?id=12432
SRHBZ #12432 does not seem to happen in a VM, but still seems to
exhibit a bad backtrace, so I see.
--
later, Robert Xu
---------------------------------------------------------------------
To unsubscribe, e-mail:
trinity-devel-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail:
trinity-devel-help(a)lists.pearsoncomputing.net
Read list messsages on the Web archive:
http://trinity-devel.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
5062
days inactive
5066
days old
14 comments
5 participants
participants (5)
-
/dev/ammo42 -
Darrell Anderson -
PICCORO McKAY Lenz -
Robert Xu -
Timothy Pearson