|
From: Christoph B. <bar...@or...> - 2006-09-05 09:09:05
Attachments:
vg.6215
|
Hi, my callgrind test crashed today during the write of the results file such that nearly all results vanished. The logfile is attached. Christoph Bartoschek |
|
From: Julian S. <js...@ac...> - 2006-09-05 14:10:50
|
> my callgrind test crashed today during the write of the results file such > that nearly all results vanished. The logfile is attached. Depending on which bug it is, it may already have been fixed. Can you re-run with --trace-syscalls=yes and send the result? J |
|
From: Christoph B. <bar...@or...> - 2006-09-05 14:33:15
|
Am Dienstag, 5. September 2006 16:09 schrieb Julian Seward: > > my callgrind test crashed today during the write of the results file such > > that nearly all results vanished. The logfile is attached. > > Depending on which bug it is, it may already have been fixed. > Can you re-run with --trace-syscalls=yes and send the result? > Hi, the run takes more than 19 hours and I guess there are a lot of syscalls during this period. Is there a way to give you the necessary information without a whole trace? Christoph |
|
From: Christoph B. <bar...@or...> - 2006-09-05 15:13:39
|
Am Dienstag, 5. September 2006 16:09 schrieb Julian Seward: > > my callgrind test crashed today during the write of the results file such > > that nearly all results vanished. The logfile is attached. > > Depending on which bug it is, it may already have been fixed. > Can you re-run with --trace-syscalls=yes and send the result? > > J Is the current repository version stable enough to use it? Then I could test whether it is already fixed. Christoph |