First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 432
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Gerd Behrmann <behrmann@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
dining cryptographers model text/xml Marius Mikucionis 2007-11-19 13:39 7.23 KB Details
queries for dining cryptographers protocol application/octet-stream Marius Mikucionis 2007-11-19 13:40 800 bytes Details
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 432 depends on: Show dependency tree
Show dependency graph
Bug 432 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: 2007-11-19 13:39
I have a model of dining cryptographers.
Currently it is hopeless that verification could scale with many cryptographers
in the system (due to unexploited ring symmetry), however UPPAAL claims to
verify the problem with 1000 cryptographers in a few seconds, that is something
I did not expect.
The closer look revealed serious correctness problems, like some trivial states
are not reachable when many processes are instantiated, but they are reached
when only a handful is used.
My guess is that there is some kind of buffer overflow problem either with
transition filter (many broadcast synchronization combinations) or template
instantiation.
The UPPAAL version from the trunk suffers the same problems, and in addition it
reports 0 time and 0 memory used, which hints that there are some stability
issues.

------- Comment #1 From Marius Mikucionis 2007-11-19 13:39:50 -------
Created an attachment (id=200) [details]
dining cryptographers model

------- Comment #2 From Marius Mikucionis 2007-11-19 13:40:23 -------
Created an attachment (id=201) [details]
queries for dining cryptographers protocol

------- Comment #3 From Alexandre David 2007-11-29 18:13:36 -------
The bug was caused by an overflow. This is detected in rev. 3350.

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