Open GoogleCodeExporter opened 9 years ago
Hi
I think your suggestion makes sense. Can you upload you bootchart.tgz file so I
can
try the crash myself?
Best
Anders
Original comment by anders.n...@gmail.com
on 29 May 2009 at 11:05
Any idea yet Anders?
My python is terrible, but it appears the _parse_timed_blocks() def needs
fixing to
allow the following part to fail:
38 try:
39 return (int(lines[0]), lines[1:])
40 except ValueError:
41 raise ParseError("expected a timed-block, but timestamp '%s' is
not an integer" % lines[0])
should be trivial to code an exception case for the "bootchartd not running"
case for
anyone who actually knows Python.
Original comment by parallel...@gmail.com
on 2 Jun 2009 at 8:06
Well, I think that the bootchart loogger somehow stopped prematurely?
So if I change the last lines of _parse_timed_blocks()
{{{
except ValueError:
if lines[0] == "bootchartd not running":
return None
raise ParseError("expected a timed-block, but timestamp '%s' is not
an integer" % lines[0])
blocks = file.read().split('\n\n')
return [parse(block) for block in blocks if block.strip() and parse(block)]
}}}
then I get past the first error. But then I get another error when parsing the
proc_ps.log file. In that file there is a newline missing at the end of the file
which gives another crash (until one adds the newline).
Do you know if the bootchart stopped prematurely?
Original comment by anders.n...@gmail.com
on 3 Jun 2009 at 1:09
bootchart was stopped using `/usr/bin/killall -USR1 bootchartd`
Which is exactly what /sbin/bootchartd in case you call it with `stop`:
quote ""killall -USR1 bootchartd"".
I suppose the real bug is in bootchartd itself, but it would be nice if
pybootchartgui would survive this.
Original comment by parallel...@gmail.com
on 3 Jun 2009 at 7:51
Original issue reported on code.google.com by
parallel...@gmail.com
on 28 May 2009 at 8:49