This issue tracker is closed. Please visit UPPAAL issue tracker at Github instead.

Bug 560 - Infimum_Cost rising to "-1073741823"
Summary: Infimum_Cost rising to "-1073741823"
Status: ASSIGNED
Alias: None
Product: UPPAAL CORA
Classification: Unclassified
Component: Verification Engine (show other bugs)
Version: 060910
Hardware: PC Other
: P5 major
Assignee: Marius Mikučionis
URL:
Depends on:
Blocks:
 
Reported: 2013-09-27 11:43 CEST by Waheed Ahmad
Modified: 2019-10-21 10:19 CEST (History)
1 user (show)

See Also:
Architecture:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Waheed Ahmad 2013-09-27 11:43:05 CEST 
Hi,
In the attached model, there are two instances of Processors "Processor0" and "Processor1" and one instance of Task_Graph. Task Graph can synchronise with both instances of Processors using channels "fire" and "end". 

Lets say we synchronise Task_graph manually with BOTH processors "Processor0" and "Processor1" in the beginning using "fire[e][a]" and then with "end[p0][a]" and "end[p1][a]". Now, if we continue in the same fashion of synchronising ALL "fire" channels first and then "end" channels manually, then infimum _cost shoots to "-1073741823". Could you please look into it as soon as possible?

I am using Windows7.

Many thanks in advance.

Regards,
Waheed Ahmad
Comment 1 Marius Mikučionis 2019-10-21 10:19:18 CEST 
Taking over