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

Bug 508 - Segmentation fault
Summary: Segmentation fault
Status: RESOLVED INVALID
Alias: None
Product: UPPAAL
Classification: Unclassified
Component: Engine (show other bugs)
Version: 4.0.8
Hardware: PC Linux
: P2 blocker
Assignee: Marius Mikučionis
URL: http://www.win.tue.nl/~atif/uppaal/ex...
Depends on:
Blocks:
 
Reported: 2011-02-20 10:55 CET by Muhammad Atif
Modified: 2019-11-25 12:00 CET (History)
2 users (show)

See Also:
Architecture:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Muhammad Atif 2011-02-20 10:55:38 CET
I am using UPPAAL 4.1.2 (rev. 4409), September 2009 Academic and non-commercial use only.I tested it even with release version
I am facing segmentation fault problem by using verifyta. 

bash-4.0$ time ./verifyta Buffer1ignore.xml deadlock.q -t0 -ftracefile.xtr -u
Options for the verification:
  Generating some trace
  Search order is breadth first
  Using conservative space optimisation
  Seed is 1298160931
  State space representation uses minimal constraint systems

Verifying property 1 at line 6
Segmentation fault (core dumped), Load: 12974374 states

real    33m56.628s
user    33m3.844s
sys     0m8.148s
Comment 1 Jimmy Merrild Krag 2011-03-01 11:28:38 CET
Have you tried other versions of UPPAAL?
E.g. The current stable version 4.0.13, or the current development snapshot version 4.1.3 (rev. 4577)?
Also, do you run it on 32 or 64 bit?
Comment 2 Marius Mikučionis 2019-11-25 12:00:08 CET
I am taking over this bug.

We need more information: in particular the model file and queries.

For now, I'll just mark it as invalid, feel free to reopen if the issue persists.