Issue in glibc in FC3T3 ?

Kim Lux (Mr.) lux at diesel-research.com
Thu Oct 28 15:41:00 UTC 2004


cat /proc/self/maps below as requested along with another bt.


Other weirdness:

I freshened qt and glibc with rpm -F.  My computer fan went nuts (I'm on
a laptop and I know when that happens that the cpu or disk is working
hard.)  I opened a Konsole and did a top and found prelink using 60 to
90% of the cpu resources.  I su'd to root did a top and killed prelink.
I closed Konsole. 

A few minutes later the fan went nuts again.  I opened another Konsole
and did a top.  I found top (AS ROOT) using 95% of the cpu resources.  I
exited, su'd and ran top again.  I killed the top that was running as
root.  I then exited Konsole with exit (to get out of su) and exit (to
get out of Konsole).

I would hazard a guess that Konsole isn't logging out users properly if
you close it while being su.  I'll bet it is leaving the su process
running and it is <eventually> running away, thus using all the computer
resources.

This might be a Konsole issue or something that supports it, ie whatever
kills users and processes when one closes Konsole. 



Program received signal SIGINT, Interrupt.
[Switching to Thread -152062272 (LWP 8640)]
0x007f74dc in memcpy () from /lib/tls/libc.so.6
(gdb) bt
#0  0x007f74dc in memcpy () from /lib/tls/libc.so.6
#1  0x02b8ab5e in QString::setLength () from /usr/lib/qt-3.3/lib/libqt-
mt.so.3
#2  0x02b8af12 in QString::grow () from /usr/lib/qt-3.3/lib/libqt-
mt.so.3
#3  0x02b8ea11 in QString::insert () from /usr/lib/qt-3.3/lib/libqt-
mt.so.3
#4  0x02b8eaa1 in QString::insert () from /usr/lib/qt-3.3/lib/libqt-
mt.so.3
#5  0xf66308ea in Lexer::nextToken ()
   from /home/krlux/kdevelop-3.1.1/lib/libkdevcppparser.so.0
#6  0xf663a0a6 in Lexer::tokenize ()
   from /home/krlux/kdevelop-3.1.1/lib/libkdevcppparser.so.0
#7  0xf663a2d0 in Lexer::setSource ()
   from /home/krlux/kdevelop-3.1.1/lib/libkdevcppparser.so.0
#8  0xf66284c6 in Driver::parseFile ()
   from /home/krlux/kdevelop-3.1.1/lib/libkdevcppparser.so.0
#9  0xf66cbd8e in CppSupportPart::slotParseFiles ()
   from /home/krlux/kdevelop-3.1.1/lib/kde3/libkdevcppsupport.so
#10 0xf66d3691 in CppSupportPart::qt_invoke ()
   from /home/krlux/kdevelop-3.1.1/lib/kde3/libkdevcppsupport.so
#11 0x028c33a0 in QObject::activate_signal ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#12 0x02bf459d in QSignal::signal () from /usr/lib/qt-3.3/lib/libqt-
mt.so.3
#13 0x028dc0dd in QSignal::activate () from /usr/lib/qt-3.3/lib/libqt-
mt.so.3
#14 0x028e319b in QSingleShotTimer::event ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
---Type <return> to continue, or q <return> to quit---
#15 0x02864849 in QApplication::internalNotify ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#16 0x028649da in QApplication::notify ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#17 0x001b94e8 in KApplication::notify () from /usr/lib/libkdecore.so.4
#18 0x02858bbe in QEventLoop::activateTimers ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#19 0x02814bde in QEventLoop::processEvents ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#20 0x02879e75 in QEventLoop::enterLoop ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#21 0x02879dce in QEventLoop::exec () from /usr/lib/qt-3.3/lib/libqt-
mt.so.3
#22 0x02863a4b in QApplication::exec () from /usr/lib/qt-3.3/lib/libqt-
mt.so.3
#23 0x0809db71 in main ()



$ cat maps
00775000-0078a000 r-xp 00000000 03:05 6193243    /lib/ld-2.3.3.so
0078a000-0078b000 r--p 00014000 03:05 6193243    /lib/ld-2.3.3.so
0078b000-0078c000 rw-p 00015000 03:05 6193243    /lib/ld-2.3.3.so
0078e000-008af000 r-xp 00000000 03:05 6258989    /lib/tls/libc-2.3.3.so
008af000-008b1000 r--p 00120000 03:05 6258989    /lib/tls/libc-2.3.3.so
008b1000-008b3000 rw-p 00122000 03:05 6258989    /lib/tls/libc-2.3.3.so
008b3000-008b5000 rw-p 008b3000 00:00 0
008dc000-008de000 r-xp 00000000 03:05 6193244    /lib/libdl-2.3.3.so
008de000-008df000 r--p 00001000 03:05 6193244    /lib/libdl-2.3.3.so
008df000-008e0000 rw-p 00002000 03:05 6193244    /lib/libdl-2.3.3.so
009cd000-009d0000 r-xp 00000000 03:05
6193280    /lib/libtermcap.so.2.0.8
009d0000-009d1000 rw-p 00002000 03:05
6193280    /lib/libtermcap.so.2.0.8
08047000-080d8000 r-xp 00000000 03:05 6045828    /bin/bash
080d8000-080de000 rw-p 00090000 03:05 6045828    /bin/bash
080de000-080e3000 rw-p 080de000 00:00 0
08caf000-08cf1000 rw-p 08caf000 00:00 0
f6dc9000-f6dd2000 r-xp 00000000 03:05
7094320    /lib/libnss_files-2.3.3.so
f6dd2000-f6dd3000 r--p 00008000 03:05
7094320    /lib/libnss_files-2.3.3.so
f6dd3000-f6dd4000 rw-p 00009000 03:05
7094320    /lib/libnss_files-2.3.3.so
f6de0000-f6de2000 rw-p f6de0000 00:00 0
f6de2000-f6de3000 r--p 002de000 03:05 2255274    /usr/lib/locale/locale-
archive
f6de3000-f6de9000 r--s 00000000 03:05 2261896    /usr/lib/gconv/gconv-
modules.cache
f6de9000-f6fe9000 r--p 00000000 03:05 2255274    /usr/lib/locale/locale-
archive
f6fe9000-f6feb000 rw-p f6fe9000 00:00 0
fef1d000-ff000000 rw-p fef1d000 00:00 0
ffffe000-fffff000 ---p 00000000 00:00 0





On Thu, 2004-28-10 at 11:00 -0400, Jakub Jelinek 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.  
> > 
> > A backtrace in gdb always shows the application crashing in the same
> > place: 
> > 
> > 0x007f74dc in memcpy () from /lib/tls/libc.so.6
> 
> Crashes in memcpy means some routine called memcpy with wrong
> arguments.  So the whole backtrace at least is needed,
> ideally together with /proc/self/maps at the point it crashes.
> 
> 	Jakub
> 
-- 
Kim Lux (Mr.) <lux at diesel-research.com>




More information about the fedora-test-list mailing list