Qt-interest Archive, December 2007
Weird core dump problems with QInotifyFileSystemWatcherEngine
Message 1 in thread
I've got an application that runs as a demon and sits and waits for
files to come in. Once they arrive it reads the file and processes the
data in the file. However, I'm getting some weird core dumps at odd
times. Odd times because it's when nothing is being processed on the
system. No files are coming in. My logs just show the demons to be
sitting their bored out of their skulls.
The annoying thing is it looks like it's dying in the library and
therefore isn't something I can really update.
Any thoughts or suggestions. The gdb where output follows.
#0 0xb738409a in QInotifyFileSystemWatcherEngine::readFromInotify ()
from /usr/lib/libQtCore.so.4
#1 0xb73cce13 in QInotifyFileSystemWatcherEngine::qt_metacall ()
from /usr/lib/libQtCore.so.4
#2 0xb73ad0ec in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#3 0xb73ad61c in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#4 0xb73ce471 in QSocketNotifier::activated () from
/usr/lib/libQtCore.so.4
#5 0xb73b4f82 in QSocketNotifier::event () from /usr/lib/libQtCore.so.4
#6 0xb77b9823 in QApplicationPrivate::notify_helper ()
from /usr/lib/libQtGui.so.4
#7 0xb77bca50 in QApplication::notify () from /usr/lib/libQtGui.so.4
#8 0xb73c08cd in socketNotifierSourceDispatch () from
/usr/lib/libQtCore.so.4
#9 0xb7243abd in g_main_context_dispatch ()
from /opt/gnome/lib/libglib-2.0.so.0
#10 0xb7246cbf in g_main_context_check () from
/opt/gnome/lib/libglib-2.0.so.0
#11 0xb7247225 in g_main_context_iteration ()
from /opt/gnome/lib/libglib-2.0.so.0
#12 0xb73c03bd in QEventDispatcherGlib::processEvents ()
from /usr/lib/libQtCore.so.4
#13 0xb739ae38 in QEventLoop::processEvents () from
/usr/lib/libQtCore.so.4
#14 0xb739afaa in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#15 0xb72eacda in QThread::exec () from /usr/lib/libQtCore.so.4
#16 0xb738393a in QInotifyFileSystemWatcherEngine::run ()
---Type <return> to continue, or q <return> to quit---
from /usr/lib/libQtCore.so.4
#17 0xb72ed654 in QThreadPrivate::start () from /usr/lib/libQtCore.so.4
#18 0xb720934b in start_thread () from /lib/libpthread.so.0
#19 0xb709065e in clone () from /lib/libc.so.6
Message 2 in thread
So no one has any ideas on this problem or requests for more information
to help nail things down?
________________________________
From: Allen, Matthew [mailto:allenm@xxxxxxxxxxxxxxxxxxxxxx]
Sent: Tuesday, December 11, 2007 10:28 AM
To: qt-interest@xxxxxxxxxxxxx
Subject: Weird core dump problems with QInotifyFileSystemWatcherEngine
I've got an application that runs as a demon and sits and waits for
files to come in. Once they arrive it reads the file and processes the
data in the file. However, I'm getting some weird core dumps at odd
times. Odd times because it's when nothing is being processed on the
system. No files are coming in. My logs just show the demons to be
sitting their bored out of their skulls.
The annoying thing is it looks like it's dying in the library and
therefore isn't something I can really update.
Any thoughts or suggestions. The gdb where output follows.
#0 0xb738409a in QInotifyFileSystemWatcherEngine::readFromInotify ()
from /usr/lib/libQtCore.so.4
#1 0xb73cce13 in QInotifyFileSystemWatcherEngine::qt_metacall ()
from /usr/lib/libQtCore.so.4
#2 0xb73ad0ec in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#3 0xb73ad61c in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#4 0xb73ce471 in QSocketNotifier::activated () from
/usr/lib/libQtCore.so.4
#5 0xb73b4f82 in QSocketNotifier::event () from /usr/lib/libQtCore.so.4
#6 0xb77b9823 in QApplicationPrivate::notify_helper ()
from /usr/lib/libQtGui.so.4
#7 0xb77bca50 in QApplication::notify () from /usr/lib/libQtGui.so.4
#8 0xb73c08cd in socketNotifierSourceDispatch () from
/usr/lib/libQtCore.so.4
#9 0xb7243abd in g_main_context_dispatch ()
from /opt/gnome/lib/libglib-2.0.so.0
#10 0xb7246cbf in g_main_context_check () from
/opt/gnome/lib/libglib-2.0.so.0
#11 0xb7247225 in g_main_context_iteration ()
from /opt/gnome/lib/libglib-2.0.so.0
#12 0xb73c03bd in QEventDispatcherGlib::processEvents ()
from /usr/lib/libQtCore.so.4
#13 0xb739ae38 in QEventLoop::processEvents () from
/usr/lib/libQtCore.so.4
#14 0xb739afaa in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#15 0xb72eacda in QThread::exec () from /usr/lib/libQtCore.so.4
#16 0xb738393a in QInotifyFileSystemWatcherEngine::run ()
---Type <return> to continue, or q <return> to quit---
from /usr/lib/libQtCore.so.4
#17 0xb72ed654 in QThreadPrivate::start () from /usr/lib/libQtCore.so.4
#18 0xb720934b in start_thread () from /lib/libpthread.so.0
#19 0xb709065e in clone () from /lib/libc.so.6
Message 3 in thread
yes, please that can help.
these days I got some BUS errors (10, 11). and still don't know from
where they came.
in your case it seems that things went wrong completely. there is a
chain of failures.
if you stop the daemon does it start ?
is your hardware ok ? did you updated something that broke everything
else that qt was dependent on ? etc..
lots of parameters can be.
Allen, Matthew wrote:
>
> So no one has any ideas on this problem or requests for more
> information to help nail things down?
>
> ------------------------------------------------------------------------
>
> *From:* Allen, Matthew [mailto:allenm@xxxxxxxxxxxxxxxxxxxxxx]
> *Sent:* Tuesday, December 11, 2007 10:28 AM
> *To:* qt-interest@xxxxxxxxxxxxx
> *Subject:* Weird core dump problems with QInotifyFileSystemWatcherEngine
>
> I’ve got an application that runs as a demon and sits and waits for
> files to come in. Once they arrive it reads the file and processes the
> data in the file. However, I’m getting some weird core dumps at odd
> times. Odd times because it’s when nothing is being processed on the
> system. No files are coming in. My logs just show the demons to be
> sitting their bored out of their skulls.
>
> The annoying thing is it looks like it’s dying in the library and
> therefore isn’t something I can really update.
>
> Any thoughts or suggestions. The gdb where output follows.
>
> #0 0xb738409a in QInotifyFileSystemWatcherEngine::readFromInotify ()
>
> from /usr/lib/libQtCore.so.4
>
> #1 0xb73cce13 in QInotifyFileSystemWatcherEngine::qt_metacall ()
>
> from /usr/lib/libQtCore.so.4
>
> #2 0xb73ad0ec in QMetaObject::activate () from /usr/lib/libQtCore.so.4
>
> #3 0xb73ad61c in QMetaObject::activate () from /usr/lib/libQtCore.so.4
>
> #4 0xb73ce471 in QSocketNotifier::activated () from
> /usr/lib/libQtCore.so.4
>
> #5 0xb73b4f82 in QSocketNotifier::event () from /usr/lib/libQtCore.so.4
>
> #6 0xb77b9823 in QApplicationPrivate::notify_helper ()
>
> from /usr/lib/libQtGui.so.4
>
> #7 0xb77bca50 in QApplication::notify () from /usr/lib/libQtGui.so.4
>
> #8 0xb73c08cd in socketNotifierSourceDispatch () from
> /usr/lib/libQtCore.so.4
>
> #9 0xb7243abd in g_main_context_dispatch ()
>
> from /opt/gnome/lib/libglib-2.0.so.0
>
> #10 0xb7246cbf in g_main_context_check () from
> /opt/gnome/lib/libglib-2.0.so.0
>
> #11 0xb7247225 in g_main_context_iteration ()
>
> from /opt/gnome/lib/libglib-2.0.so.0
>
> #12 0xb73c03bd in QEventDispatcherGlib::processEvents ()
>
> from /usr/lib/libQtCore.so.4
>
> #13 0xb739ae38 in QEventLoop::processEvents () from
> /usr/lib/libQtCore.so.4
>
> #14 0xb739afaa in QEventLoop::exec () from /usr/lib/libQtCore.so.4
>
> #15 0xb72eacda in QThread::exec () from /usr/lib/libQtCore.so.4
>
> #16 0xb738393a in QInotifyFileSystemWatcherEngine::run ()
>
> ---Type <return> to continue, or q <return> to quit---
>
> from /usr/lib/libQtCore.so.4
>
> #17 0xb72ed654 in QThreadPrivate::start () from /usr/lib/libQtCore.so.4
>
> #18 0xb720934b in start_thread () from /lib/libpthread.so.0
>
> #19 0xb709065e in clone () from /lib/libc.so.6
>
--
[ signature omitted ]
Message 4 in thread
Yes, I can restart the demon with no trouble. I have a script that if it
seems the demon die it restarts it and it's working fine.
Hardware is ok. It's happening on more than one machine. I haven't
updated anything new. It's been happening kinda randomly for months no
but recently it got worse at one of the install locations.
It does seem to happen around 2am and 7:30pm more often than not. But I
haven't found anything that should cause the library to die.
-----Original Message-----
From: Yong Taro [mailto:yanicher@xxxxxxxxx]
Sent: Wednesday, December 12, 2007 12:09 PM
To: qt-interest@xxxxxxxxxxxxx
Subject: Re: Weird core dump problems with
QInotifyFileSystemWatcherEngine
yes, please that can help.
these days I got some BUS errors (10, 11). and still don't know from
where they came.
in your case it seems that things went wrong completely. there is a
chain of failures.
if you stop the daemon does it start ?
is your hardware ok ? did you updated something that broke everything
else that qt was dependent on ? etc..
lots of parameters can be.
Allen, Matthew wrote:
>
> So no one has any ideas on this problem or requests for more
> information to help nail things down?
>
>
------------------------------------------------------------------------
>
> *From:* Allen, Matthew [mailto:allenm@xxxxxxxxxxxxxxxxxxxxxx]
> *Sent:* Tuesday, December 11, 2007 10:28 AM
> *To:* qt-interest@xxxxxxxxxxxxx
> *Subject:* Weird core dump problems with
QInotifyFileSystemWatcherEngine
>
> I've got an application that runs as a demon and sits and waits for
> files to come in. Once they arrive it reads the file and processes the
> data in the file. However, I'm getting some weird core dumps at odd
> times. Odd times because it's when nothing is being processed on the
> system. No files are coming in. My logs just show the demons to be
> sitting their bored out of their skulls.
>
> The annoying thing is it looks like it's dying in the library and
> therefore isn't something I can really update.
>
> Any thoughts or suggestions. The gdb where output follows.
>
> #0 0xb738409a in QInotifyFileSystemWatcherEngine::readFromInotify ()
>
> from /usr/lib/libQtCore.so.4
>
> #1 0xb73cce13 in QInotifyFileSystemWatcherEngine::qt_metacall ()
>
> from /usr/lib/libQtCore.so.4
>
> #2 0xb73ad0ec in QMetaObject::activate () from /usr/lib/libQtCore.so.4
>
> #3 0xb73ad61c in QMetaObject::activate () from /usr/lib/libQtCore.so.4
>
> #4 0xb73ce471 in QSocketNotifier::activated () from
> /usr/lib/libQtCore.so.4
>
> #5 0xb73b4f82 in QSocketNotifier::event () from
/usr/lib/libQtCore.so.4
>
> #6 0xb77b9823 in QApplicationPrivate::notify_helper ()
>
> from /usr/lib/libQtGui.so.4
>
> #7 0xb77bca50 in QApplication::notify () from /usr/lib/libQtGui.so.4
>
> #8 0xb73c08cd in socketNotifierSourceDispatch () from
> /usr/lib/libQtCore.so.4
>
> #9 0xb7243abd in g_main_context_dispatch ()
>
> from /opt/gnome/lib/libglib-2.0.so.0
>
> #10 0xb7246cbf in g_main_context_check () from
> /opt/gnome/lib/libglib-2.0.so.0
>
> #11 0xb7247225 in g_main_context_iteration ()
>
> from /opt/gnome/lib/libglib-2.0.so.0
>
> #12 0xb73c03bd in QEventDispatcherGlib::processEvents ()
>
> from /usr/lib/libQtCore.so.4
>
> #13 0xb739ae38 in QEventLoop::processEvents () from
> /usr/lib/libQtCore.so.4
>
> #14 0xb739afaa in QEventLoop::exec () from /usr/lib/libQtCore.so.4
>
> #15 0xb72eacda in QThread::exec () from /usr/lib/libQtCore.so.4
>
> #16 0xb738393a in QInotifyFileSystemWatcherEngine::run ()
>
> ---Type <return> to continue, or q <return> to quit---
>
> from /usr/lib/libQtCore.so.4
>
> #17 0xb72ed654 in QThreadPrivate::start () from
/usr/lib/libQtCore.so.4
>
> #18 0xb720934b in start_thread () from /lib/libpthread.so.0
>
> #19 0xb709065e in clone () from /lib/libc.so.6
>
--
[ signature omitted ]
