About the Execution of PeCan for DLCshifumi-PT-3a
Execution Summary | |||||
Max Memory Used (MB) |
Time wait (ms) | CPU Usage (ms) | I/O Wait (ms) | Computed Result | Execution Status |
3133.850 | 54349.00 | 54233.00 | 667.60 | F??????????????? | 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 DLCshifumi-PT-3a, examination is LTLFireability
Time confinement is 3600 seconds
Memory confinement is 16384 MBytes
Number of cores is 1
Run identifier is r225su-smll-146468036700204
=====================================================================
--------------------
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 DLCshifumi-PT-3a-LTLFireability-0
FORMULA_NAME DLCshifumi-PT-3a-LTLFireability-1
FORMULA_NAME DLCshifumi-PT-3a-LTLFireability-10
FORMULA_NAME DLCshifumi-PT-3a-LTLFireability-11
FORMULA_NAME DLCshifumi-PT-3a-LTLFireability-12
FORMULA_NAME DLCshifumi-PT-3a-LTLFireability-13
FORMULA_NAME DLCshifumi-PT-3a-LTLFireability-14
FORMULA_NAME DLCshifumi-PT-3a-LTLFireability-15
FORMULA_NAME DLCshifumi-PT-3a-LTLFireability-2
FORMULA_NAME DLCshifumi-PT-3a-LTLFireability-3
FORMULA_NAME DLCshifumi-PT-3a-LTLFireability-4
FORMULA_NAME DLCshifumi-PT-3a-LTLFireability-5
FORMULA_NAME DLCshifumi-PT-3a-LTLFireability-6
FORMULA_NAME DLCshifumi-PT-3a-LTLFireability-7
FORMULA_NAME DLCshifumi-PT-3a-LTLFireability-8
FORMULA_NAME DLCshifumi-PT-3a-LTLFireability-9
=== Now, execution of the tool begins
BK_START 1464956891871
=====================================================================
Generated by BenchKit MCC2016
Executing tool pecan:
Test is DLCshifumi-PT-3a, examination is LTLFireability
=====================================================================
--------------------
content from stdout:
START 1464956891
Xlib: extension "RANDR" missing on display ":99".
DLCshifumiPT3aToo many heap sections: Increase MAXHINCR or MAX_HEAP_SECTS
Stacktrace:
at (wrapper managed-to-native) object.__icall_wrapper_mono_string_alloc (intptr) <0xffffffff>
at (wrapper alloc) object.Alloc (intptr,int) <0xffffffff>
at string.Concat (string,string) <0x0005f>
at PAT.Common.Classes.Expressions.Valuation.GetID () <0x0016b>
at PAT.Common.Classes.Expressions.Valuation.GetID (string) <0x00013>
at PAT.PN.LTS.PNConfiguration.GetID () <0x00075>
at PAT.Common.Classes.ModuleInterface.ConfigurationBase.GetIDWithEvent () <0x00013>
at PAT.Common.Classes.SemanticModels.LTS.Assertion.AssertionLTL.TarjanModelChecking () <0x00bb1>
at PAT.Common.Classes.SemanticModels.LTS.Assertion.AssertionLTL.RunVerification () <0x0020f>
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)
Native stacktrace:
/usr/bin/mono() [0x80e16fc]
[0xb776240c]
[0xb7762424]
/lib/i386-linux-gnu/libc.so.6(gsignal+0x4f) [0xb757e20f]
/lib/i386-linux-gnu/libc.so.6(abort+0x175) [0xb7581855]
/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() [0x8226743]
/usr/bin/mono(mono_string_new_size+0x45) [0x81a67e5]
/usr/bin/mono() [0x81a6888]
[0xb7022940]
[0xb7022904]
[0xb702cca0]
[0xb247d96c]
[0xb247d7e4]
[0xb247d71e]
[0xb247d684]
[0xb2461bb2]
[0xb247c968]
[0xb247c6fb]
[0xb247c088]
[0xb5d5b100]
[0xb701f370]
[0xb701f89f]
/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 DLCshifumi-PT-3a-LTLFireability-0 FALSE TECHNIQUES EXPLICIT
FORMULA DLCshifumi-PT-3a-LTLFireability-1
FORMULA DLCshifumi-PT-3a-LTLFireability-2
FORMULA DLCshifumi-PT-3a-LTLFireability-3
FORMULA DLCshifumi-PT-3a-LTLFireability-4
FORMULA DLCshifumi-PT-3a-LTLFireability-5
FORMULA DLCshifumi-PT-3a-LTLFireability-6
FORMULA DLCshifumi-PT-3a-LTLFireability-7
FORMULA DLCshifumi-PT-3a-LTLFireability-8
FORMULA DLCshifumi-PT-3a-LTLFireability-9
FORMULA DLCshifumi-PT-3a-LTLFireability-10
FORMULA DLCshifumi-PT-3a-LTLFireability-11
FORMULA DLCshifumi-PT-3a-LTLFireability-12
FORMULA DLCshifumi-PT-3a-LTLFireability-13
FORMULA DLCshifumi-PT-3a-LTLFireability-14
FORMULA DLCshifumi-PT-3a-LTLFireability-15
STOP 1464956946
--------------------
content from stderr:
--------------------
content from /root/BK_RESULTS/OUTPUTS/BenchKit_head_log_file.1820:
BK_STOP 1464956946220
--------------------
content from stderr:
cat: /root/BK_RESULTS/OUTPUTS/STDERR: Permission denied
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="DLCshifumi-PT-3a"
export BK_EXAMINATION="LTLFireability"
export BK_TOOL="pecan"
export BK_RESULT_DIR="/root/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/DLCshifumi-PT-3a.tgz
mv DLCshifumi-PT-3a 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 DLCshifumi-PT-3a, examination is LTLFireability"
echo " Time confinement is $BK_TIME_CONFINEMENT seconds"
echo " Memory confinement is 16384 MBytes"
echo " Number of cores is 1"
echo " Run identifier is r225su-smll-146468036700204"
echo "====================================================================="
echo
echo "--------------------"
echo "content from stdout:"
echo
echo "=== Data for post analysis generated by BenchKit (invocation template)"
echo
if [ "LTLFireability" = "UpperBounds" ] ; then
echo "The expected result is a vector of positive values"
echo NUM_VECTOR
elif [ "LTLFireability" != "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 "LTLFireability.txt" ] ; then
echo "here is the order used to build the result vector(from text file)"
for x in $(grep Property LTLFireability.txt | cut -d ' ' -f 2 | sort -u) ; do
echo "FORMULA_NAME $x"
done
elif [ -f "LTLFireability.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 ;