First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 454
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Alexandre David <adavid@cs.aau.dk>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Marius Mikucionis <marius@cs.aau.dk>
Add CC:
CC:
URL:
Summary:

Attachment Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 454 depends on: Show dependency tree
Show dependency graph
Bug 454 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments:







View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2008-12-18 18:35
I think this bug is a release critical, so just for the record:

1) There is no documentation about stopwatches in the manual,
i.e. how to define, use them and what are consequences.

2) safety verification suddenly switches to "probably" and does not give any
trace, although the verification terminates quite quickly, i.e. it clearly
found something, but refuses to show it. 

I'd like to get that trace, even if that is an overapproximation, or at least
show a reason in status why there is no trace when trace is requested.

Is it a fundamental/correctness problem or implementation limitation?

------- Comment #1 From Alexandre David 2009-03-10 11:19:01 -------
Fixed in rev. 4247.

First Last Prev Next    No search results available      Search page      Enter new bug