Share

EiskaltDC

Tracker: Bugs

5 eiskaltdc не корректно обрабатывает SIGTERM - ID: 2895916
Last Update: Settings changed ( rasenherz )

Вместо корректного выхода из приложения,
появляется главное окно (до этого он
свернут в трей). По сути SIGTERM делает toggle
для главного окна. При выходе из kde eiskaltdc
выкидывает окно отладки (скорее всего
это тоже связано с неверной обработкой
SIGTERM)


Nobody/Anonymous ( nobody ) - 2009-11-11 13:32

5

Closed

Fixed

Nobody/Anonymous

None

None

Public


Comments ( 10 )

Date: 2009-11-28 18:21
Sender: nobody

Fixed. Thanks.


Date: 2009-11-28 18:03
Sender: rasenherzProject Admin

Try out r613


Date: 2009-11-28 16:45
Sender: rasenherzProject Admin

Ok, i'll fix this bug tonight


Date: 2009-11-28 16:39
Sender: nobody

I guess that problem is in INotify Control.
When I try to disable it from the menu I had this:

Program received signal SIGSEGV, Segmentation fault.
~DCInotifyControl (this=0x86659d0, __in_chrg=<value optimized out>)
at
/media/ext3/Linux/eiskalt/eiskalt-svn/eiskaltdc/dcinotifycontrol.cpp:87
87 killTimer(collector->timerId());




Date: 2009-11-28 16:31
Sender: nobody

Thanks for explanation.
Here is log:
Exiting...
[Thread 0xb7618b70 (LWP 3733) exited]

Program received signal SIGSEGV, Segmentation fault.
0x00383f89 in ~DCInotifyControl (this=0x8678360,
__in_chrg=<value optimized out>)
at
/media/ext3/Linux/eiskalt/eiskalt-svn/eiskaltdc/dcinotifycontrol.cpp:84
84 delete timer;

And backtrace is:
#0 0x00383f89 in ~DCInotifyControl (this=0x8678360,
__in_chrg=<value optimized out>)
at
/media/ext3/Linux/eiskalt/eiskalt-svn/eiskaltdc/dcinotifycontrol.cpp:84
#1 0x033b646f in QObjectPrivate::deleteChildren (this=0x84b86e8)
at kernel/qobject.cpp:1847
#2 0x00e3685b in ~QWidget (this=0x8480ca0,
__in_chrg=<value optimized out>) at kernel/qwidget.cpp:1367
#3 0x012073e1 in ~QMainWindow (this=0x8480ca0,
__in_chrg=<value optimized out>)
at widgets/qmainwindow.cpp:331
#4 0x003488da in ~DCGuiApp (this=0x8480ca0,
__in_chrg=<value optimized out>)
at /media/ext3/Linux/eiskalt/eiskalt-svn/eiskaltdc/dcgui.cpp:351
#5 0x0804cf88 in main (argc=4553076, argv=0xbffff924)
at /media/ext3/Linux/eiskalt/eiskalt-svn/eiskaltdc/main.cpp:538


Date: 2009-11-28 16:21
Sender: rasenherzProject Admin

just run in console: gdb eiskaltdc (gdb must be installed)
when program crashes type into gdb "backtrace" + <Enter> and post output
in this topic.


Date: 2009-11-28 16:06
Sender: nobody

I have never done it. So I can try, but if it's not so hard for you, please
explain how to do it.


Date: 2009-11-28 15:58
Sender: rasenherzProject Admin

Can you build client with debug info? Please, send me backtrace from GDB.


Date: 2009-11-28 15:37
Sender: nobody

I still have this prolem.
Program crashed every time I closed it.
Here is log:
Object::disconnect: No such signal QMdiSubWindow::onDie(QWidget*)
Object::disconnect: No such signal QMdiSubWindow::onDie(QWidget*)
Object::disconnect: No such signal QMdiSubWindow::onDie(QWidget*)
Object::disconnect: No such signal QMdiSubWindow::onDie(QWidget*)
Exiting...
EiskaltDC: '1.0.35' using dclib: '0.3.24svn'
Checking Qt® version... compiled for '4.5.2' using '4.5.2'
handle crash
handle crash
fcntl flock: Resource temporarily unavailable
Checking libxml2 version... compiled for '20705' using '20705'
CRASH: (null) 2221,11,/usr/local/bin/eiskaltdc
Init debug:
Configpath: ''
2221 11 /usr/local/bin/eiskaltdc
exit


Date: 2009-11-23 17:45
Sender: rasenherzProject Admin

Fixed


Attached File

No Files Currently Attached

Changes ( 7 )

Field Old Value Date By
close_date 2009-11-23 17:45 2009-11-28 18:26 rasenherz
allow_comments 1 2009-11-28 18:26 rasenherz
status_id Open 2009-11-28 18:26 rasenherz
status_id Closed 2009-11-28 15:37 nobody
status_id Open 2009-11-23 17:45 rasenherz
resolution_id None 2009-11-23 17:45 rasenherz
close_date - 2009-11-23 17:45 rasenherz