This forum has been archived. All content is frozen. Please use KDE Discuss instead.

Program received signal SIG43 [564414]

Page 1 of 1 (5 posts)

Tags: None
(comma "," separated)
snap
Registered Member
Posts
20
Karma
0

Program received signal SIG43 [564414]

Thu Jul 20, 2006 7:15 am
everytime i make a su - root ktorrent crashes with a SIG43.

This happened first after i installed the autobuild tool for www.linuxfromscratch.org yesterday.

The newest SVN does not help.

If this problem is not directly related to ktorrent, but something else, im terribly sorry.

(gdb) run --debug --nofork
Starting program: /usr/bin/ktorrent --debug --nofork
[Thread debugging using libthread_db enabled]
[New Thread 16384 (LWP 18196)]
[New Thread 32769 (LWP 18209)]
[New Thread 16386 (LWP 18210)]

Program received signal SIG43, Real-time event 43.
[Switching to Thread 16384 (LWP 18196)]
0x00002aace168e246 in select () from /lib/libc.so.6
(gdb) bt
#0 0x00002aace168e246 in select () from /lib/libc.so.6
#1 0x00002aacdf2ce8a8 in QEventLoop::processEvents () from /usr/qt/3/lib64/libqt-mt.so.3
#2 0x00002aacdf3313a1 in QEventLoop::enterLoop () from /usr/qt/3/lib64/libqt-mt.so.3
#3 0x00002aacdf3312f5 in QEventLoop::exec () from /usr/qt/3/lib64/libqt-mt.so.3
#4 0x000000000041e5ec in main (argc=3, argv=0x7fffffdcbe38) at main.cpp:115
imported4-Ivan
Registered Member
Posts
819
Karma
0

Thu Jul 20, 2006 10:29 am
It seems to me that this is not KT related. It stops with a signal in the middle of Qt code so I don't think there's much we can do.

Maybe this autobuild tool caused some troubles to your system?
snap
Registered Member
Posts
20
Karma
0

Thu Jul 20, 2006 1:49 pm
i hope not >.> but i just ordered gdb not to pass through that signal so it runs fine at the moment :D.
George
Moderator
Posts
5421
Karma
1

Thu Jul 20, 2006 7:41 pm
Last time I checked that signal did not have any influence on ktorrent (kill -43 <pid-of-ktorent>)

EDIT: it seems it does have influence

The question is were does this signal come from ?
snap
Registered Member
Posts
20
Karma
0

Fri Jul 21, 2006 4:19 pm
for me it works with su - root, but only if i need to enter the password. Everytime that happens, i get 4x SIG43.

I searched around with google and it looks like it is an signal used by libc, so it is no error, as it appears in gdb... [checks some more stuff]

Page 1 of 1 (5 posts)

Bookmarks


Who is online

Registered users: Bing [Bot], Evergrowing, Google [Bot]