Bug 223565 - Application crashes when I load a different type input file
Summary: Application crashes when I load a different type input file
Status: RESOLVED WORKSFORME
Alias: None
Product: kstars
Classification: Applications
Component: general (other bugs)
Version First Reported In: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Akarsh Simha
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2010-01-20 12:57 UTC by Efthymis
Modified: 2018-10-27 02:16 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Efthymis 2010-01-20 12:57:15 UTC
Version:            (using KDE 4.3.2)
OS:                Linux

OS: Ubuntu 9.10, Karmic Koala, 64-bit version.
I downloaded "Kstars" using Ubuntu software center.

Go to :
(From main menu) --> Tools --> Calculator --> Coordinate Converters --> * (any of the listed options) --> Batch mode --> Input file --> enter a random input file.

I expected that if the file was not what the program expected, an information message would appear and the application would continue to run.
Instead of this, the application crashed.

(I'll post the backtrace, after I install valgrind)
Comment 1 Jérôme SONRIER 2010-02-01 15:39:10 UTC
You can get backtraces without installing valgrind :
http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports
Comment 2 Lukas 2010-02-01 23:23:16 UTC
I can confirm this with trunk r1083751 on fedora 12.

debug output states

ASSERT failure in QList<T>::operator[]: "index out of range", file /usr/include/QtCore/qlist.h, line 447

bt is

Application: KStars (kstars), signal: Aborted
82	T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[KCrash Handler]
#5  0x0000003c65c326c5 in raise (sig=<value optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#6  0x0000003c65c33ea5 in abort () at abort.c:92
#7  0x0000003950669a54 in qt_message_output (msgType=<value optimized out>, buf=<value optimized out>) at global/qglobal.cpp:2250
#8  0x0000003950669c32 in qt_message(QtMsgType, const char *, typedef __va_list_tag __va_list_tag *) (msgType=QtFatalMsg, msg=0x39507add98 "ASSERT failure in %s: \"%s\", file %s, line %d", ap=
    0x7fff6225e3f0) at global/qglobal.cpp:2296
#9  0x0000003950669de5 in qFatal (msg=0x1cd7 <Address 0x1cd7 out of bounds>) at global/qglobal.cpp:2479
#10 0x0000000000457bff in QList<QString>::operator[] (this=0x7fff6225e5a0, i=1) at /usr/include/QtCore/qlist.h:447
#11 0x00000000004e9013 in modCalcApCoord::processLines (this=0x39ef1a0, istream=...) at /home/kde-devel/kde/src/trunk/KDE/kdeedu/kstars/kstars/tools/modcalcapcoord.cpp:235
#12 0x00000000004e8b43 in modCalcApCoord::slotRunBatch (this=0x39ef1a0) at /home/kde-devel/kde/src/trunk/KDE/kdeedu/kstars/kstars/tools/modcalcapcoord.cpp:174
#13 0x00000000004e98ea in modCalcApCoord::qt_metacall (this=0x39ef1a0, _c=InvokeMetaMethod, _id=10, _a=0x7fff6225ea20)
    at /home/kde-devel/kde/build/trunk/KDE/kdeedu/kstars/kstars/modcalcapcoord.moc:99
#14 0x0000003950768adf in QMetaObject::activate (sender=0x3f59a20, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x7fff6225ea20) at kernel/qobject.cpp:3275
#15 0x00000039529dc5e2 in QAbstractButton::clicked (this=<value optimized out>, _t1=false) at .moc/release-shared/moc_qabstractbutton.cpp:206
#16 0x000000395272df8b in QAbstractButtonPrivate::emitClicked (this=0x3f59a60) at widgets/qabstractbutton.cpp:546
#17 0x000000395272f1fb in QAbstractButtonPrivate::click (this=0x3f59a60) at widgets/qabstractbutton.cpp:539
#18 0x000000395272f46c in QAbstractButton::mouseReleaseEvent (this=0x3f59a20, e=0x7fff6225f3a0) at widgets/qabstractbutton.cpp:1121
#19 0x00000039523f585a in QWidget::event (this=0x3f59a20, event=0x7fff6225f3a0) at kernel/qwidget.cpp:7978
#20 0x00000039523aa86c in QApplicationPrivate::notify_helper (this=0x1aca2f0, receiver=0x3f59a20, e=0x7fff6225f3a0) at kernel/qapplication.cpp:4298
#21 0x00000039523b110d in QApplication::notify (this=<value optimized out>, receiver=0x3f59a20, e=0x7fff6225f3a0) at kernel/qapplication.cpp:3863
#22 0x00007f84f15c3b7f in KApplication::notify (this=0x7fff62260390, receiver=0x3f59a20, event=0x7fff6225f3a0) at /home/kde-devel/kde/src/trunk/KDE/kdelibs/kdeui/kernel/kapplication.cpp:302
#23 0x000000395075696c in QCoreApplication::notifyInternal (this=0x7fff62260390, receiver=0x3f59a20, event=0x7fff6225f3a0) at kernel/qcoreapplication.cpp:704
#24 0x00000039523b02fe in sendEvent (receiver=0x3f59a20, event=0x7fff6225f3a0, alienWidget=0x3f59a20, nativeWidget=0x3a131c0, buttonDown=<value optimized out>, 
    lastMouseReceiver=<value optimized out>, spontaneous=<value optimized out>) at ../../src/corelib/kernel/qcoreapplication.h:215
#25 QApplicationPrivate::sendMouseEvent (receiver=0x3f59a20, event=0x7fff6225f3a0, alienWidget=0x3f59a20, nativeWidget=0x3a131c0, buttonDown=<value optimized out>, 
    lastMouseReceiver=<value optimized out>, spontaneous=<value optimized out>) at kernel/qapplication.cpp:2963
#26 0x0000003952421d65 in QETWidget::translateMouseEvent (this=0x3a131c0, event=<value optimized out>) at kernel/qapplication_x11.cpp:4368
#27 0x0000003952420a88 in QApplication::x11ProcessEvent (this=<value optimized out>, event=0x7fff6225fcc0) at kernel/qapplication_x11.cpp:3501
#28 0x00000039524496b2 in x11EventSourceDispatch (s=0x1ace090, callback=<value optimized out>, user_data=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:146
#29 0x0000003c6903922e in g_main_dispatch (context=0x1acd120) at gmain.c:1960
#30 IA__g_main_context_dispatch (context=0x1acd120) at gmain.c:2513
#31 0x0000003c6903cc18 in g_main_context_iterate (context=0x1acd120, block=<value optimized out>, dispatch=<value optimized out>, self=<value optimized out>) at gmain.c:2591
#32 0x0000003c6903cd3a in IA__g_main_context_iteration (context=0x1acd120, may_block=1) at gmain.c:2654
#33 0x000000395077c2b3 in QEventDispatcherGlib::processEvents (this=0x1aae1f0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:412
#34 0x000000395244937e in QGuiEventDispatcherGlib::processEvents (this=<value optimized out>, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#35 0x00000039507553b2 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#36 0x000000395075567c in QEventLoop::exec (this=0x7fff6225fff0, flags=...) at kernel/qeventloop.cpp:201
#37 0x0000003950757969 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981
#38 0x00000000005cfaae in main (argc=1, argv=0x7fff62260fa8) at /home/kde-devel/kde/src/trunk/KDE/kdeedu/kstars/kstars/main.cpp:191
Comment 3 Tadas 2010-08-30 06:42:04 UTC
This bug should be closed as Fixed, because in Kstars 1.6.0 it doesn't crash ant it show a message about an invalid file. Only one thing could be done. The Run button could be disabled until you put info about both of those files, just like in all the entries from [Time Calculators].

P.s
[Solar system] -> [Planet Coordinates] doesn't crash, but it doesn't show Invalid File dialog, when Run is pressed.
Comment 4 Christoph Feck 2013-09-12 21:44:46 UTC
This crash report is at least 3 years old and there were no further comments or status updates since then.

Therefore we believe that this crash is already fixed in recent KDE 4 versions or the backtrace is no longer applicable to the current KDE 4 sources.

If the crash still happens with a recent KDE version (4.10.5 or 4.11), please add an updated backtrace or provide steps to reproduce. For more information, see http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

(To prevent automatic closing of this bug in the future, please set the bug status to ASSIGNED or CONFIRMED)
Comment 5 Andrew Crouthamel 2018-09-24 02:00:42 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Andrew Crouthamel 2018-10-27 02:16:22 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!