[filelight] [Bug 368154] filelight crashes if invoked without a directory parameter

2018-04-04 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=368154

kwanza.p...@virginmedia.com changed:

   What|Removed |Added

 Resolution|--- |WONTFIX
 Status|UNCONFIRMED |RESOLVED

-- 
You are receiving this mail because:
You are watching all bug changes.

[filelight] [Bug 368154] filelight crashes if invoked without a directory parameter

2016-09-04 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=368154

--- Comment #2 from p...@kc.rr.com ---
Thanks. The output from valgrind is shown below:

Found the following remote filesystems:  ()
Found the following local filesystems:  ("/home/", "/boot/", "/opt/", "/tmp/",
"
/usr/src/", "/var/", "/local/")
==10565== Warning: invalid file descriptor 1024 in syscall close()
==10565== Warning: invalid file descriptor 1025 in syscall close()
==10565== Warning: invalid file descriptor 1026 in syscall close()
==10565== Warning: invalid file descriptor 1027 in syscall close()
==10565==Use --log-fd= to select an alternative log fd.
==10565== Warning: invalid file descriptor 1028 in syscall close()
==10565== Warning: invalid file descriptor 1029 in syscall close()
==10544== Invalid read of size 8
==10544==at 0x184B3313: RadialMap::Map::paint(bool) (map.cpp:322)
==10544==by 0x6B5B991: QWidget::event(QEvent*) (in
/opt/kde/lib64/libQt5Widg
ets.so.5.7.0)
==10544==by 0x6B17A2B: QApplicationPrivate::notify_helper(QObject*,
QEvent*)
 (in /opt/kde/lib64/libQt5Widgets.so.5.7.0)
==10544==by 0x6B1EBE0: QApplication::notify(QObject*, QEvent*) (in
/opt/kde/
lib64/libQt5Widgets.so.5.7.0)
==10544==by 0x79E0687: QCoreApplication::notifyInternal2(QObject*, QEvent*)
(in /opt/kde/lib64/libQt5Core.so.5.7.0)
==10544==by 0x6B4DAD3: QWidgetPrivate::propagatePaletteChange() (in
/opt/kde
/lib64/libQt5Widgets.so.5.7.0)
==10544==by 0x6B4DCC4: QWidgetPrivate::setPalette_helper(QPalette const&)
(i
n /opt/kde/lib64/libQt5Widgets.so.5.7.0)
==10544==by 0x6B4DD3D: QWidgetPrivate::resolvePalette() (in
/opt/kde/lib64/l
ibQt5Widgets.so.5.7.0)
==10544==by 0x6B4DB4B: QWidgetPrivate::propagatePaletteChange() (in
/opt/kde
/lib64/libQt5Widgets.so.5.7.0)
==10544==by 0x6B4DCC4: QWidgetPrivate::setPalette_helper(QPalette const&)
(i
n /opt/kde/lib64/libQt5Widgets.so.5.7.0)
==10544==by 0x6B4DD3D: QWidgetPrivate::resolvePalette() (in
/opt/kde/lib64/l
ibQt5Widgets.so.5.7.0)
==10544==by 0x6B4DB4B: QWidgetPrivate::propagatePaletteChange() (in
/opt/kde
/lib64/libQt5Widgets.so.5.7.0)
==10544==  Address 0x90 is not stack'd, malloc'd or (recently) free'd
==10544==
==10544==
==10544== Process terminating with default action of signal 11 (SIGSEGV)
==10544==  Access not within mapped region at address 0x90
==10544==at 0x184B3313: RadialMap::Map::paint(bool) (map.cpp:322)
==10544==by 0x6B5B991: QWidget::event(QEvent*) (in
/opt/kde/lib64/libQt5Widg
ets.so.5.7.0)
==10544==by 0x6B17A2B: QApplicationPrivate::notify_helper(QObject*,
QEvent*)
 (in /opt/kde/lib64/libQt5Widgets.so.5.7.0)
==10544==by 0x6B1EBE0: QApplication::notify(QObject*, QEvent*) (in
/opt/kde/
lib64/libQt5Widgets.so.5.7.0)
==10544==by 0x79E0687: QCoreApplication::notifyInternal2(QObject*, QEvent*)
(in /opt/kde/lib64/libQt5Core.so.5.7.0)
==10544==by 0x6B4DAD3: QWidgetPrivate::propagatePaletteChange() (in
/opt/kde
/lib64/libQt5Widgets.so.5.7.0)
==10544==by 0x6B4DCC4: QWidgetPrivate::setPalette_helper(QPalette const&)
(i
n /opt/kde/lib64/libQt5Widgets.so.5.7.0)
==10544==by 0x6B4DD3D: QWidgetPrivate::resolvePalette() (in
/opt/kde/lib64/l
ibQt5Widgets.so.5.7.0)
==10544==by 0x6B4DB4B: QWidgetPrivate::propagatePaletteChange() (in
/opt/kde
/lib64/libQt5Widgets.so.5.7.0)
==10544==by 0x6B4DCC4: QWidgetPrivate::setPalette_helper(QPalette const&)
(i
n /opt/kde/lib64/libQt5Widgets.so.5.7.0)
==10544==by 0x6B4DD3D: QWidgetPrivate::resolvePalette() (in
/opt/kde/lib64/l
ibQt5Widgets.so.5.7.0)
==10544==by 0x6B4DB4B: QWidgetPrivate::propagatePaletteChange() (in
/opt/kde
/lib64/libQt5Widgets.so.5.7.0)
==10544==  If you believe this happened as a result of a stack
==10544==  overflow in your program's main thread (unlikely but
==10544==  possible), you can try to increase the size of the
==10544==  main thread stack using the --main-stacksize= flag.
==10544==  The main thread stack size used in this run was 8388608.
==10544==
==10544== HEAP SUMMARY:
==10544== in use at exit: 4,892,462 bytes in 47,584 blocks
==10544==   total heap usage: 485,350 allocs, 437,766 frees, 2,685,711,896
bytes
 allocated
==10544==
==10544== 80 bytes in 1 blocks are possibly lost in loss record 2,950 of 4,827
==10544==at 0x4C2B11F: malloc (in
/usr/lib64/valgrind/vgpreload_memcheck-amd
64-linux.so)
==10544==by 0xE7E7888: __glDispatchInit (in /usr/lib64/libGLdispatch.so.0)
==10544==by 0xE58F6E4: _init (in /usr/lib64/libGLX.so.0)
==10544==by 0x400F429: call_init.part.0 (in /lib64/ld-2.24.so)
==10544==by 0x400F57A: _dl_init (in /lib64/ld-2.24.so)
==10544==by 0x4000CF9: ??? (in /lib64/ld-2.24.so)
==10544==
==10544== 80 bytes in 1 blocks are possibly lost in loss record 2,951 of 4,827
==10544==at 0x4C2B11F: malloc (in
/usr/lib64/valgrind/vgpreload_memcheck-amd
64-linux.so)
==10544==by 0xE7E84BA: __glDispatchRegisterStubCallbacks (in
/usr/lib64/libG
Ldispatch.so.0)
==10544==by 0xACC474A: _init (in /usr/lib64/libGL.so.1.0.0)
==10544==by 

[filelight] [Bug 368154] filelight crashes if invoked without a directory parameter

2016-09-04 Thread Martin Sandsmark via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=368154

Martin Sandsmark  changed:

   What|Removed |Added

Summary|filelight crashes if|filelight crashes if
   |invoked with a directory|invoked without a directory
   |parameter   |parameter

-- 
You are receiving this mail because:
You are watching all bug changes.


[filelight] [Bug 368154] filelight crashes if invoked with a directory parameter

2016-09-04 Thread Martin Sandsmark via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=368154

--- Comment #1 from Martin Sandsmark  ---
Can't reproduce it here.

Extremely weird place to crash, the line is «a[0] = a[2] - a_max / 2;», and a
is a normal stack-allocated uint array.

Can you try running it with valgrind, and see if anything interesting pops up
before it crashes?

-- 
You are receiving this mail because:
You are watching all bug changes.

[filelight] [Bug 368154] filelight crashes if invoked with a directory parameter

2016-09-03 Thread Christoph Feck via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=368154

Christoph Feck  changed:

   What|Removed |Added

   Severity|normal  |crash

-- 
You are receiving this mail because:
You are watching all bug changes.