fond
Model Checking Contest @ Petri Nets 2016
6th edition, Toruń, Poland, June 21, 2016
Execution of r213su-blw3-146445842300243
Last Updated
June 30, 2016

About the Execution of PeCan for AutoFlight-PT-05a

Execution Summary
Max Memory
Used (MB)
Time wait (ms) CPU Usage (ms) I/O Wait (ms) Computed Result Execution
Status
3275.350 787711.00 788132.00 60.00 TT??????T??????? normal

Execution Chart

We display below the execution chart for this examination (boot time has been removed).

Trace from the execution

Waiting for the VM to be ready (probing ssh)
............
=====================================================================
Generated by BenchKit 2-2979
Executing tool pecan
Input is AutoFlight-PT-05a, examination is ReachabilityFireability
Time confinement is 3600 seconds
Memory confinement is 16384 MBytes
Number of cores is 1
Run identifier is r213su-blw3-146445842300243
=====================================================================


--------------------
content from stdout:

=== Data for post analysis generated by BenchKit (invocation template)

The expected result is a vector of booleans
BOOL_VECTOR

here is the order used to build the result vector(from text file)
FORMULA_NAME AutoFlight-PT-05a-ReachabilityFireability-0
FORMULA_NAME AutoFlight-PT-05a-ReachabilityFireability-1
FORMULA_NAME AutoFlight-PT-05a-ReachabilityFireability-10
FORMULA_NAME AutoFlight-PT-05a-ReachabilityFireability-11
FORMULA_NAME AutoFlight-PT-05a-ReachabilityFireability-12
FORMULA_NAME AutoFlight-PT-05a-ReachabilityFireability-13
FORMULA_NAME AutoFlight-PT-05a-ReachabilityFireability-14
FORMULA_NAME AutoFlight-PT-05a-ReachabilityFireability-15
FORMULA_NAME AutoFlight-PT-05a-ReachabilityFireability-2
FORMULA_NAME AutoFlight-PT-05a-ReachabilityFireability-3
FORMULA_NAME AutoFlight-PT-05a-ReachabilityFireability-4
FORMULA_NAME AutoFlight-PT-05a-ReachabilityFireability-5
FORMULA_NAME AutoFlight-PT-05a-ReachabilityFireability-6
FORMULA_NAME AutoFlight-PT-05a-ReachabilityFireability-7
FORMULA_NAME AutoFlight-PT-05a-ReachabilityFireability-8
FORMULA_NAME AutoFlight-PT-05a-ReachabilityFireability-9

=== Now, execution of the tool begins

BK_START 1464768057731

=====================================================================
Generated by BenchKit MCC2016
Executing tool pecan:
Test is AutoFlight-PT-05a, examination is ReachabilityFireability
=====================================================================

--------------------
content from stdout:

START 1464768057
Xlib: extension "RANDR" missing on display ":99".
AutoFlightPT05aToo many heap sections: Increase MAXHINCR or MAX_HEAP_SECTS
Stacktrace:

at (wrapper managed-to-native) object.__icall_wrapper_mono_object_new_fast (intptr) <0xffffffff>
at PAT.Common.Classes.Expressions.Valuation.GetVariableClone () <0x000c3>
at PAT.PN.LTS.PNConfiguration.MakeOneMove () <0x000e4>
at PAT.Common.Classes.SemanticModels.LTS.Assertion.AssertionLTL.DFSVerification () <0x00275>
at PAT.Common.Classes.SemanticModels.LTS.Assertion.AssertionLTL.RunVerification () <0x001cb>
at PAT.Common.Classes.ModuleInterface.AssertionBase.ModelChecking () <0x00012>
at PAT.Common.Classes.ModuleInterface.AssertionBase.InternalStart () <0x00077>
at PAT.Console.Program.RunOneSpec (string,string,System.IO.StreamWriter,System.Text.StringBuilder,bool,bool,int,int,string) <0x00187>
at PAT.Console.Program.Main (string[]) <0x0152f>
at (wrapper runtime-invoke) .runtime_invoke_void_object (object,intptr,intptr,intptr) <0xffffffff>

Native stacktrace:

/usr/bin/mono() [0x80e16fc]
[0xb77a340c]
[0xb77a3424]
/lib/i386-linux-gnu/libc.so.6(gsignal+0x4f) [0xb75bf20f]
/lib/i386-linux-gnu/libc.so.6(abort+0x175) [0xb75c2855]
/usr/bin/mono() [0x8223e76]
/usr/bin/mono() [0x821cb24]
/usr/bin/mono() [0x821cd3a]
/usr/bin/mono() [0x821cff8]
/usr/bin/mono() [0x821d13a]
/usr/bin/mono() [0x821fb39]
/usr/bin/mono() [0x8220890]
/usr/bin/mono() [0x8226838]
/usr/bin/mono(mono_object_new_fast+0x18) [0x81a1d18]
[0xb7060ae8]
[0xb3cf8ebc]
[0xb3cf749d]
[0xb3cd9f0e]
[0xb3cf58b4]
[0xb3cf568b]
[0xb3cf46d8]
[0xb5d9c100]
[0xb7060370]
[0xb706089f]
/usr/bin/mono() [0x8064c2c]

Debug info from gdb:

Could not attach to process. If your uid matches the uid of the target
process, check the setting of /proc/sys/kernel/yama/ptrace_scope, or try
again as the root user. For more details, see /etc/sysctl.d/10-ptrace.conf
ptrace: Operation not permitted.
No threads.

=================================================================
Got a SIGABRT while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.
=================================================================

Aborted (core dumped)
FORMULA AutoFlight-PT-05a-ReachabilityFireability-0 TRUE TECHNIQUES EXPLICIT
FORMULA AutoFlight-PT-05a-ReachabilityFireability-1 TRUE TECHNIQUES EXPLICIT
FORMULA AutoFlight-PT-05a-ReachabilityFireability-2 TRUE TECHNIQUES EXPLICIT
FORMULA AutoFlight-PT-05a-ReachabilityFireability-3
FORMULA AutoFlight-PT-05a-ReachabilityFireability-4
FORMULA AutoFlight-PT-05a-ReachabilityFireability-5
FORMULA AutoFlight-PT-05a-ReachabilityFireability-6
FORMULA AutoFlight-PT-05a-ReachabilityFireability-7
FORMULA AutoFlight-PT-05a-ReachabilityFireability-8
FORMULA AutoFlight-PT-05a-ReachabilityFireability-9
FORMULA AutoFlight-PT-05a-ReachabilityFireability-10
FORMULA AutoFlight-PT-05a-ReachabilityFireability-11
FORMULA AutoFlight-PT-05a-ReachabilityFireability-12
FORMULA AutoFlight-PT-05a-ReachabilityFireability-13
FORMULA AutoFlight-PT-05a-ReachabilityFireability-14
FORMULA AutoFlight-PT-05a-ReachabilityFireability-15
STOP 1464768845

--------------------
content from stderr:


--------------------
content from /home/hulinhub/BK_RESULTS/OUTPUTS/BenchKit_head_log_file.1840:


BK_STOP 1464768845442

--------------------
content from stderr:

cat: /home/hulinhub/BK_RESULTS/OUTPUTS/STDERR: No such file or directory

Sequence of Actions to be Executed by the VM

This is useful if one wants to reexecute the tool in the VM from the submitted image disk.

set -x
# this is for BenchKit: configuration of major elements for the test
export BK_INPUT="AutoFlight-PT-05a"
export BK_EXAMINATION="ReachabilityFireability"
export BK_TOOL="pecan"
export BK_RESULT_DIR="/home/hulinhub/BK_RESULTS/OUTPUTS"
export BK_TIME_CONFINEMENT="3600"
export BK_MEMORY_CONFINEMENT="16384"

# this is specific to your benchmark or test

export BIN_DIR="$HOME/BenchKit/bin"

# remove the execution directoty if it exists (to avoid increse of .vmdk images)
if [ -d execution ] ; then
rm -rf execution
fi

tar xzf /home/mcc/BenchKit/INPUTS/AutoFlight-PT-05a.tgz
mv AutoFlight-PT-05a execution

# this is for BenchKit: explicit launching of the test

cd execution
echo "====================================================================="
echo " Generated by BenchKit 2-2979"
echo " Executing tool pecan"
echo " Input is AutoFlight-PT-05a, examination is ReachabilityFireability"
echo " Time confinement is $BK_TIME_CONFINEMENT seconds"
echo " Memory confinement is 16384 MBytes"
echo " Number of cores is 1"
echo " Run identifier is r213su-blw3-146445842300243"
echo "====================================================================="
echo
echo "--------------------"
echo "content from stdout:"
echo
echo "=== Data for post analysis generated by BenchKit (invocation template)"
echo
if [ "ReachabilityFireability" = "UpperBounds" ] ; then
echo "The expected result is a vector of positive values"
echo NUM_VECTOR
elif [ "ReachabilityFireability" != "StateSpace" ] ; then
echo "The expected result is a vector of booleans"
echo BOOL_VECTOR
else
echo "no data necessary for post analysis"
fi
echo
if [ -f "ReachabilityFireability.txt" ] ; then
echo "here is the order used to build the result vector(from text file)"
for x in $(grep Property ReachabilityFireability.txt | cut -d ' ' -f 2 | sort -u) ; do
echo "FORMULA_NAME $x"
done
elif [ -f "ReachabilityFireability.xml" ] ; then # for cunf (txt files deleted;-)
echo echo "here is the order used to build the result vector(from xml file)"
for x in $(grep '' ReachabilityFireability.xml | cut -d '>' -f 2 | cut -d '<' -f 1 | sort -u) ; do
echo "FORMULA_NAME $x"
done
fi
echo
echo "=== Now, execution of the tool begins"
echo
echo -n "BK_START "
date -u +%s%3N
echo
timeout -s 9 $BK_TIME_CONFINEMENT bash -c "/home/mcc/BenchKit/BenchKit_head.sh 2> STDERR ; echo ; echo -n \"BK_STOP \" ; date -u +%s%3N"
if [ $? -eq 137 ] ; then
echo
echo "BK_TIME_CONFINEMENT_REACHED"
fi
echo
echo "--------------------"
echo "content from stderr:"
echo
cat STDERR ;