About the Execution of LTSMin for S_RwMutex-PT-r2000w0010
Execution Summary | |||||
Max Memory Used (MB) |
Time wait (ms) | CPU Usage (ms) | I/O Wait (ms) | Computed Result | Execution Status |
11680.570 | 645431.00 | 1181058.00 | 195.00 | ? | 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-2265
Executing tool ltsmin
Input is S_RwMutex-PT-r2000w0010, examination is ReachabilityDeadlock
Time confinement is 3600 seconds
Memory confinement is 16384 MBytes
Number of cores is 4
Run identifier is r273st-qhx2-143374439700167
=====================================================================
--------------------
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 RwMutex-PT-r2000w0010-ReachabilityDeadlock-0
=== Now, execution of the tool begins
BK_START 1434012291725
FORMULA RwMutex-PT-r2000w0010-ReachabilityDeadlock-0 CANNOT_COMPUTE
BK_STOP 1434012937156
--------------------
content from stderr:
property name is RwMutex-PT-r2000w0010-ReachabilityDeadlock-0
Initializing Lace, 0 nodes, 4 cores, 4 logical processors, 4 workers.
pins2lts-sym: Using 4 CPUs
pins2lts-sym: Exploration order is chain
pins2lts-sym: Saturation strategy is sat-like
pins2lts-sym: Guided search strategy is unguided
pins2lts-sym: Attractor strategy is default
pins2lts-sym: Registering PINS so language module
pins2lts-sym: Main process: 0.
Lace startup, creating 4 worker threads with program stack 8388608 bytes.
pins2lts-sym: opening model.so
pins2lts-sym: library has no initializer
pins2lts-sym: loading model PNML
pins2lts-sym: completed loading model PNML
pins2lts-sym: Regroup specification: cn,w2W,ru,lb:cs.rs.cw:cs.rs.cs,rs,vf
pins2lts-sym: Regroup Column Nub
pins2lts-sym: Regroup over-approximate must-write to may-write
pins2lts-sym: Regroup Row sUbsume
pins2lts-sym: Regroup Lowest Bandwidth
pins2lts-sym: Computing lowest bandwidth in: ":cs.rs.cw:cs.rs.cs"
pins2lts-sym: Bandwidth of may-write matrix with sequence "ε": 4018045
pins2lts-sym: Regroup Column Sort
pins2lts-sym: Regroup Row Sort
pins2lts-sym: Regroup Column sWaps
pins2lts-sym: Bandwidth of may-write matrix with sequence "cs.rs.cw": 802385
pins2lts-sym: Regroup Column Sort
pins2lts-sym: Regroup Row Sort
pins2lts-sym: Regroup Column Sort
pins2lts-sym: Bandwidth of may-write matrix with sequence "cs.rs.cs": 4014047
pins2lts-sym: Regroup Row Sort
pins2lts-sym: Reqroup Vertical Flip
pins2lts-sym: Regrouping: 4020->2010 groups
pins2lts-sym: state vector length is 6020; there are 2010 groups and 6020 guards
pins2lts-sym: Creating a multi-core ListDD domain.
pins2lts-sym: Using GBgetTransitionsShort as next-state function
pins2lts-sym: got initial state
pins2lts-sym: vrel_add_act not supported; falling back to vrel_add_cpy
*** segmentation fault ***
Please send information on how to reproduce this problem to:
ltsmin-support@lists.utwente.nl
along with all output preceding this message.
In addition, include the following information:
Package: ltsmin 2.1
Stack trace:
0: pins2lts-sym(HREprintStack+0x1a) [0x43b51a]
1: pins2lts-sym() [0x43b586]
2: /lib/x86_64-linux-gnu/libpthread.so.0(+0xf0a0) [0x7fdd5daf00a0]
3: /lib/x86_64-linux-gnu/libc.so.6(+0x121d23) [0x7fdd5d0d7d23]
4: /home/mcc/gitprojects/ltsmin/sylvan/.libs/libsylvan.so.0(lddmc_collect_CALL+0x33b) [0x7fdd5e9f2e5b]
5: /home/mcc/gitprojects/ltsmin/sylvan/.libs/libsylvan.so.0(lddmc_collect_CALL+0x177) [0x7fdd5e9f2c97]
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="S_RwMutex-PT-r2000w0010"
export BK_EXAMINATION="ReachabilityDeadlock"
export BK_TOOL="ltsmin"
export BK_RESULT_DIR="/home/fko/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/S_RwMutex-PT-r2000w0010.tgz
mv S_RwMutex-PT-r2000w0010 execution
# this is for BenchKit: explicit launching of the test
cd execution
echo "====================================================================="
echo " Generated by BenchKit 2-2265"
echo " Executing tool ltsmin"
echo " Input is S_RwMutex-PT-r2000w0010, examination is ReachabilityDeadlock"
echo " Time confinement is $BK_TIME_CONFINEMENT seconds"
echo " Memory confinement is 16384 MBytes"
echo " Number of cores is 4"
echo " Run identifier is r273st-qhx2-143374439700167"
echo "====================================================================="
echo
echo "--------------------"
echo "content from stdout:"
echo
echo "=== Data for post analysis generated by BenchKit (invocation template)"
echo
if [ "ReachabilityDeadlock" = "ReachabilityComputeBounds" ] ; then
echo "The expected result is a vector of positive values"
echo NUM_VECTOR
elif [ "ReachabilityDeadlock" != "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 "ReachabilityDeadlock.txt" ] ; then
echo "here is the order used to build the result vector(from text file)"
for x in $(grep Property ReachabilityDeadlock.txt | cut -d ' ' -f 2 | sort -u) ; do
echo "FORMULA_NAME $x"
done
elif [ -f "ReachabilityDeadlock.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 '
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 ;