Summary: | kst eventually crashes when plotting live data from dirfile with time interpretation. | ||
---|---|---|---|
Product: | [Applications] kst | Reporter: | Matthew Truch <matt> |
Component: | datasources | Assignee: | kst |
Status: | RESOLVED REMIND | ||
Severity: | crash | ||
Priority: | NOR | ||
Version: | 1.x | ||
Target Milestone: | --- | ||
Platform: | Slackware | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | kst file used during crash |
Description
Matthew Truch
2005-05-01 23:14:46 UTC
Created attachment 10871 [details]
kst file used during crash
Attached is the kst file that is used when we get the crash. It also crashed
when we generated the same plots from scratch (before we had saved this kst
file for the first time).
It doesn't appear to be connected to interpreting the field as a time. Rather it appears to have something to do with interpreting the LINCOM. The crash occurs even when not interpreting the X axis as a time. The offending field is defined as Time LINCOM 2 cpu_time 1.000000000000e+00 0.000000000000e+00 cpu_usec 1.000000000000e-06 0.000000000000e+00 where cpu_time and cpu_usec are the seconds and microseconds returned by gettimeofday(2). Backtrace for kst 1.1.0 from yesterday's anonCVS: *** glibc detected *** free(): invalid next size (fast): 0x086229f0 *** Program received signal SIGABRT, Aborted. [Switching to Thread 16386 (LWP 17768)] 0xb6596ef1 in kill () from /lib/libc.so.6 (gdb) bt #0 0xb6596ef1 in kill () from /lib/libc.so.6 #1 0xb6791bb1 in pthread_kill () from /lib/libpthread.so.0 #2 0xb6791f2b in raise () from /lib/libpthread.so.0 #3 0xb6596b24 in raise () from /lib/libc.so.6 #4 0xb65983fd in abort () from /lib/libc.so.6 #5 0xb65c976c in __libc_message () from /lib/libc.so.6 #6 0xb65d2066 in malloc_printerr () from /lib/libc.so.6 #7 0xb65d0d2f in _int_free () from /lib/libc.so.6 #8 0xb65cf94f in free () from /lib/libc.so.6 #9 0xb6295284 in GetFormat () from /opt/kde/lib/kde3/kstdata_dirfile.so #10 0xb6295cfa in MakeDummyLinterp () from /opt/kde/lib/kde3/kstdata_dirfile.so #11 0xb6295ec5 in GetData () from /opt/kde/lib/kde3/kstdata_dirfile.so #12 0xb629232c in DirFileSource::readField () from /opt/kde/lib/kde3/kstdata_dirfile.so #13 0xb62b90f9 in IndirectSource::readField () from /opt/kde/lib/kde3/kstdata_indirect.so #14 0xb7c89f06 in KstRVector::doUpdate () from /opt/kde/lib/libkstmath.so.1 #15 0xb7c898cf in KstRVector::update () from /opt/kde/lib/libkstmath.so.1 #16 0xb7c5df3e in KstVCurve::update () from /opt/kde/lib/libkstmath.so.1 #17 0xb7f1d4bc in UpdateThread::doUpdates () from /opt/kde/lib/libkstapp.so.1 #18 0xb7f1d126 in UpdateThread::run () from /opt/kde/lib/libkstapp.so.1 #19 0xb6cde02a in QThreadInstance::start () from /usr/lib/qt/lib/libqt-mt.so.3 #20 0xb678f54e in pthread_start_thread () from /lib/libpthread.so.0 #21 0xb678f5df in pthread_start_thread_event () from /lib/libpthread.so.0 #22 0xb6627b8a in clone () from /lib/libc.so.6 Ah, looks easy to track down now. Can you send me your datafile+kstfile? I really need a testcase for this if you want it fixed in 1.1.1 I can't reproduce it either, and I am looking at the same data, but on a different machine with a different dist. I will get the cryo guys here to try with 1.1.0 now that it is installed. On May 22, 2005 17:22, George Staikos wrote: [bugs.kde.org quoted mail] No testcase, can't reproduce. |