Re: Issue in glibc in FC3T3 ?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



It is kdevelop-3.1.1  I don't think that is an FC application ?

I've had 2 errors involving Qt3.3.3, which is what is calling glibc: 

This one was near login: 

Using host libthread_db library "/lib/tls/libthread_db.so.1".
[KCrash handler]
#5  0x0676b207 in operator== () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#6  0x000001f4 in ?? () from /lib/libdl.so.2
#7  0x067686d1 in QString::operator+= ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3


This one occurs regularly in kdevelop: 

#0  0x007f74dc in memcpy () from /lib/tls/libc.so.6
#1  0x04c73b5e in QString::setLength () from /usr/lib/qt-3.3/lib/libqt-
mt.so.3
#2  0x04c73f12 in QString::grow () from /usr/lib/qt-3.3/lib/libqt-
mt.so.3
#3  0x04c77a11 in QString::insert () from /usr/lib/qt-3.3/lib/libqt-
mt.so.3
#4  0x04c77aa1 in QString::insert () from /usr/lib/qt-3.3/lib/libqt-
mt.so.3
#5  0xf65608ea in Lexer::nextToken ()
   from /home/krlux/kdevelop-3.1.1/lib/libkdevcppparser.so.0
#6  0xf656a0a6 in Lexer::tokenize ()
   from /home/krlux/kdevelop-3.1.1/lib/libkdevcppparser.so.0
#7  0xf656a2d0 in Lexer::setSource ()
   from /home/krlux/kdevelop-3.1.1/lib/libkdevcppparser.so.0
#8  0xf65584c6 in Driver::parseFile ()
   from /home/krlux/kdevelop-3.1.1/lib/libkdevcppparser.so.0
#9  0xf65fbd8e in CppSupportPart::slotParseFiles ()
   from /home/krlux/kdevelop-3.1.1/lib/kde3/libkdevcppsupport.so
#10 0xf6603691 in CppSupportPart::qt_invoke ()
   from /home/krlux/kdevelop-3.1.1/lib/kde3/libkdevcppsupport.so
#11 0x049ac3a0 in QObject::activate_signal ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3

Note that qt is calling glibc.

I did a freshen of both Qt and Glibc and now I've got prelink and ld
running as root !!!!???? Prelink is stealing all my cpu cycles.  What is
up with that ?  I finally had to kill it..


On Thu, 2004-28-10 at 15:58 +0100, Tim Waugh wrote:
> On Thu, Oct 28, 2004 at 08:35:41AM -0600, Kim Lux (Mr.) wrote:
> 
> > I've got an application semi randomly crashing in FC3T3.  
> 
> Which application?  If it's a Fedora Core application, please file a
> bug against it.
> 
> > A backtrace in gdb always shows the application crashing in the same
> > place: 
> > 
> > 0x007f74dc in memcpy () from /lib/tls/libc.so.6
> 
> So perhaps memcpy was passed an invalid pointer?
> 
> Tim.
> */
> -- 
> fedora-test-list mailing list
> fedora-test-list@xxxxxxxxxx
> To unsubscribe: 
> http://www.redhat.com/mailman/listinfo/fedora-test-list
-- 
Kim Lux (Mr.) <lux@xxxxxxxxxxxxxxxxxxx>


[Index of Archives]     [Fedora Desktop]     [Fedora SELinux]     [Photo Sharing]     [Yosemite Forum]     [KDE Users]