[Kst] [Bug 116461] New: getdata borks when the first field in the format file isn't (ASCII) alphabetically the first field.
matt at truch.net
Wed Nov 16 00:55:26 CET 2005
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
Summary: getdata borks when the first field in the format file
isn't (ASCII) alphabetically the first field.
AssignedTo: kst kde org
ReportedBy: matt truch net
Version: 1.2.0_svn_480257 (using KDE KDE 3.4.2)
Currently a dirfiles 'length' (number of frames) is defined by the first (valid) field in the format file. Traditionally (on BLAST at least) this field is called FORMAT and (most) other fields are in lowercase. The fact that the number of frames is defined by the first field is important so that data writing programs can write the first field last so that the race condition of not having some of the data written yet bug doesn't come to light. However, getdata sorts the raw field list (with qsort), so the first field in the format file isn't neccesarily the first field in the list. This can cause kst to either report the wrong number of frames available (if the number of samples per frame and/or size of the type differ) or the race condition mentioned above.
More information about the Kst