PB'05 competition: run trace

Some explanations

A solver is run under the control of another program named runsolver. runsolver is in charge of imposing the CPU time limit and the memory limit to the solver. It also monitors some information about the process. The trace of the execution of a solver is divided in four parts:

LAUNCHER DATA
These informations are related to the script which will launch the solver. The most important informations are the command line given to the solver, the md5sum of the different files and the dump of the /proc/cpuinfo and /proc/meminfo which provide some useful information on the computer.
SOLVER DATA
This is the output of the solver (stdout and stderr).
WATCHER DATA
This is the informations gathered by the runsolver program. It first prints the different limits. There's a first limit on CPU time set to 1200 seconds. After this time has ellapsed, runsolver sends a SIGTERM and 2 seconds later a SIGKILL to the solver. For safety, there's also another limit set to 1230 seconds which will send a SIGXPU to the solver. The last limit is on the virtual memory used by the process (900Mb).
Every ten seconds, the runsolver process fetches the content of /proc/loadavg, /proc/pid/stat and /proc/pid/statm (see man proc) and prints it as raw data. This is only recorded in case we need to investigate the behaviour of a solver. The memory used by the solver (vsize) is also given every ten seconds.
When the solver exits, runsolver prints some informations such as status and time. CPU usage is the ratio CPU Time/Real Time.
VERIFIER DATA
The output of the solver is piped to a verifier program which will search a value line "v " and, if found, will check that the given interpretation satisfies all constraints.

General information on the benchmark

Name	normalized-opb/mps-v2-20-10/MIPLIB/miplib/normalized-mps-v2-20-10-sample2.opb
MD5SUM	bdfddb0d042ec1aadcf4263f803cbd6f
Bench Category	optimization, big integers (OPTBIGINT)
Has Objective Function	YES
Satisfiable	YES
(Un)Satisfiability was proved	YES
Best value of the objective function	384000
Optimality of the best value was proved	NO
Number of terms in the objective function	729
Biggest coefficient in the objective function	3221225472
Number of bits for the biggest coefficient in the objective function	32
Sum of the numbers in the objective function	70867574718
Number of bits of the sum of numbers in the objective function	37
Biggest number in a constraint	3221225472
Number of bits of the biggest number in a constraint	32
Biggest sum of numbers in a constraint	70867574718
Number of bits of the biggest sum of numbers	37
Best result obtained on this benchmark	SAT
Best CPU time to get the best result obtained on this benchmark	47.9837
Number of variables	1296
Total number of constraints	67
Number of constraints which are clauses	0
Number of constraints which are cardinality constraints (but not clauses)	24
Number of constraints which are nor clauses,nor cardinality constraints	43
Minimum length of a constraint	1
Maximum length of a constraint	150

Trace number 34097

#### BEGIN LAUNCHER DATA ####
LAUNCH ON wulflinc19 THE 2005-05-27 19:42:56 (client local time)
PB2005-SCRIPT v4.0 
MARKUPS: idlaunch=12254 boxname=wulflinc19 idbench=943 idsolver=8 numberseed=0
MD5SUM SOLVER: 4b637b3b6117f2add1a6288e91336322  /oldhome/oroussel/solvers/vallstSAT2005PB.sh
MD5SUM BENCH:  bdfddb0d042ec1aadcf4263f803cbd6f  /oldhome/oroussel/tmp/wulflinc19/normalized-mps-v2-20-10-sample2.opb
REAL COMMAND:  vallstSAT2005PB.sh /oldhome/oroussel/tmp/wulflinc19/normalized-mps-v2-20-10-sample2.opb 0
IDLAUNCH: 12254
/proc/cpuinfo:
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 7
model name	: Pentium III (Katmai)
stepping	: 3
cpu MHz		: 451.037
cache size	: 512 KB
fdiv_bug	: no
hlt_bug		: no
f00f_bug	: no
coma_bug	: no
fpu		: yes
fpu_exception	: yes
cpuid level	: 2
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 mmx fxsr sse
bogomips	: 890.88

processor	: 1
vendor_id	: GenuineIntel
cpu family	: 6
model		: 7
model name	: Pentium III (Katmai)
stepping	: 3
cpu MHz		: 451.037
cache size	: 512 KB
fdiv_bug	: no
hlt_bug		: no
f00f_bug	: no
coma_bug	: no
fpu		: yes
fpu_exception	: yes
cpuid level	: 2
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 mmx fxsr sse
bogomips	: 899.07

/proc/meminfo:
MemTotal:      1034660 kB
MemFree:        351232 kB
Buffers:         32280 kB
Cached:         625452 kB
SwapCached:       3840 kB
Active:          50156 kB
Inactive:       612916 kB
HighTotal:      131008 kB
HighFree:          252 kB
LowTotal:       903652 kB
LowFree:        350980 kB
SwapTotal:     2097892 kB
SwapFree:      2093360 kB
Dirty:              48 kB
Writeback:           0 kB
Mapped:           5444 kB
Slab:            14700 kB
Committed_AS:    63592 kB
PageTables:        316 kB
VmallocTotal:   114680 kB
VmallocUsed:      1368 kB
VmallocChunk:   113252 kB
JOB ENDED THE 2005-05-27 19:43:17 (client local time) WITH STATUS 0 IN 20.2519 SECONDS
stats: 12254 7 20.2519 0
#### END LAUNCHER DATA ####
#### BEGIN SOLVER DATA ####
1:
/oldhome/oroussel/solvers/vallstSAT2005PB.sh: line 175: 14684 Segmentation fault      $vallstcom --pb --complete-model=yes --first-restart=$firstrestart --improve-proof-level=0 --abort-threshold=60 --no-abort-time=300 --result-file=${tmpdir}/vallst_sh_tmp_subdir_${d}/vallst_sh.model --nr-of-vars-set-at-start-is-zero=yes "$@" --seed=$seed $problemfile --var-map-file-name=${tmpdir}/vallst_sh_tmp_subdir_${d}/vallst_var_map --out-theory-file-name=${tmpdir}/vallst_sh_tmp_subdir_${d}/vallst_sh_out_theory.vnf --changing-setting-file-name=${tmpdir}/vallst_sh_tmp_subdir_${d}/vallst_sh_changing_setting.options
times:
0m0.017s 0m0.010s
0m19.891s 0m0.270s
s UNKNOWN
#### END SOLVER DATA ####
#### BEGIN WATCHER DATA ####
Enforcing CPU limit (will send SIGTERM then SIGKILL): 1200 seconds
Enforcing CPUTime (will send SIGXCPU) limit: 1230 seconds
Enforcing VSIZE limit: 943718400 bytes
Enforcing Stack size limit: 67108864 bytes
Current StackSize limit: 67108864 bytes
Raw data (loadavg): 0.74 0.94 0.91 2/54 14681
Raw data (stat): 14681 (runsolver) R 14680 10795 10794 0 -1 64 8 0 0 0 0 0 0 0 19 0 1 0 858762717 884736 94 4294967295 134512640 135332820 3221224448 3221219612 135092226 0 2147483391 7 90112 0 0 0 17 1 0 0
Raw data (statm): 216 94 205 205 0 11 0
vsize: 864
[startup+10.0014 s]
Raw data (loadavg): 0.78 0.94 0.91 2/55 14684
Raw data (stat): 14681 (vallstSAT2005PB) S 14680 10795 10794 0 -1 0 321 232 0 0 0 0 0 0 20 0 1 0 858762717 2179072 242 4294967295 134512640 135087896 3221224512 3221223784 1074634510 0 65536 5 1132560122 3222414538 0 0 17 1 0 0
Raw data (statm): 532 242 485 147 0 385 0
vsize: 2128
[startup+20.0023 s]
Raw data (loadavg): 0.81 0.94 0.91 2/55 14684
Raw data (stat): 14681 (vallstSAT2005PB) S 14680 10795 10794 0 -1 0 321 232 0 0 0 0 0 0 20 0 1 0 858762717 2179072 242 4294967295 134512640 135087896 3221224512 3221223784 1074634510 0 65536 5 1132560122 3222414538 0 0 17 1 0 0
Raw data (statm): 532 242 485 147 0 385 0
vsize: 2128
[startup+20.6517 s]
Raw data (loadavg): 0.81 0.94 0.91 1/53 14688
Raw data (stat): 14681 (vallstSAT2005PB) S 14680 10795 10794 0 -1 0 321 232 0 0 0 0 0 0 20 0 1 0 858762717 2179072 242 4294967295 134512640 135087896 3221224512 3221223784 1074634510 0 65536 5 1132560122 3222414538 0 0 17 1 0 0
Raw data (statm): 532 242 485 147 0 385 0
vsize: 0

Child status: 0
Real time (s): 20.6515
CPU time (s): 20.2519
CPU user time (s): 19.931
CPU system time (s): 0.320951
CPU usage (%): 98.0653
Max. virtual memory (Kb): 2128
#### END WATCHER DATA ####
#### BEGIN VERIFIER DATA ####
ERROR: no interpretation found !
#### END VERIFIER DATA ####