Trace number 299221

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 into four (or five) parts:
  1. SOLVER DATA
    This is the output of the solver (stdout and stderr).
    Note that some very long lines in this section may be truncated by your web browser ! In such a case, you may want to use the "Download as text" link to get the trace as a text file.

    When the --timestamp option is passed to the runsolver program, each line output by the solver is prepended with a timestamp which indicates at what time the line was output by the solver. Times are relative to the start of the program, given in seconds, and are wall clock time (not CPU time).

    As some 'v lines' may be very long (sometimes several megabytes), the 'v line' output by your solver may be split on several lines to help limit the size of the trace recorded in the database. In any case, the exact output of your solver is preserved in a trace file.
  2. 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.
  3. CONVERSION SCRIPT DATA (Optionnal)
    When a conversion script is used, this section shows the messages that were output by the conversion script.
  4. 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 X seconds (see the parameters in the trace). 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 X+30 seconds which will send a SIGXPU to the solver. The last limit is on the virtual memory used by the process (see the parameters in the trace).
    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.
  5. 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 provides some useful information on the computer.

Solver answer on this benchmark

Solver NameAnswerCPU timeWall clock time
Mmisat 2007-02-08Signal 0.419936 0.421925

General information on the benchmark

Namerandom/OnTreshold/3SAT/v600/
unif-k3-r4.261-v600-c2556-S1104692480-03.SAT.shuffled.cnf
MD5SUMe1848ef5581233d7edc388a9e0c74c1a
Bench CategoryRANDOM (random instances)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.020996
Satisfiable
(Un)Satisfiability was proved
Number of variables600
Number of clauses2556
Sum of the clauses size7668
Maximum clause length3
Minimum clause length3
Number of clauses of size 10
Number of clauses of size 20
Number of clauses of size 32556
Number of clauses of size 40
Number of clauses of size 50
Number of clauses of size over 50

Solver Data (download as text)

0.30/0.40	terminate called after throwing an instance of 'std::bad_alloc'
0.30/0.40	  what():  St9bad_alloc

Verifier Data (download as text)

ERROR: Unexpected answer ! (SATISFIABLE/UNSATISFIABLE expected)
Got answer:

Watcher Data (download as text)

runsolver version 3.2.0 (c) roussel@cril.univ-artois.fr

command line: runsolver --timestamp -w ROOT/results/node76/watcher-299221-1171868014 -o ROOT/results/node76/solver-299221-1171868014 -C 1200 -M 1800 --output-limit 1,15 /tmp/evaluation/299221-1171868014/mmisat /tmp/evaluation/299221-1171868014/instance-299221-1171868014.cnf 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 1200 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 1230 seconds
Enforcing VSIZE limit (soft limit, will send SIGTERM then SIGKILL): 1843200 KiB
Enforcing VSIZE limit (hard limit, stack expansion will fail with SIGSEGV, brk() and mmap() will return ENOMEM): 1894400 KiB
Solver output will be limited to a maximum of 15728640 bytes. The first 1048576 bytes and the last 14680064 bytes will be preserved
Current StackSize limit: 10240 KiB


[startup+0 s]
/proc/loadavg: 1.00 1.02 1.00 3/69 17914
/proc/meminfo: memFree=1132800/2055888 swapFree=4087076/4096564
[pid=17914] ppid=17912 vsize=1176 CPUtime=0
/proc/17914/stat : 17914 (mmisat) R 17912 17914 17638 0 -1 4194304 149 0 0 0 0 0 0 0 18 0 1 0 206759697 1204224 133 18446744073709551615 134512640 135391789 4294956720 18446744073709551615 134998823 0 0 4096 0 0 0 0 17 1 0 0
/proc/17914/statm: 294 133 81 214 0 76 0

[startup+0.106333 s]
/proc/loadavg: 1.00 1.02 1.00 3/69 17914
/proc/meminfo: memFree=1132800/2055888 swapFree=4087076/4096564
[pid=17914] ppid=17912 vsize=1836 CPUtime=0.1
/proc/17914/stat : 17914 (mmisat) R 17912 17914 17638 0 -1 4194304 320 0 0 0 10 0 0 0 18 0 1 0 206759697 1880064 304 18446744073709551615 134512640 135391789 4294956720 18446744073709551615 134517190 0 0 4096 0 0 0 0 17 1 0 0
/proc/17914/statm: 459 304 81 214 0 241 0
Current children cumulated CPU time (s) 0.1
Current children cumulated vsize (KiB) 1836

Solver just ended. Dumping a history of the last processes samples

[startup+0.412369 s]
/proc/loadavg: 1.00 1.02 1.00 3/69 17914
/proc/meminfo: memFree=1132800/2055888 swapFree=4087076/4096564
[pid=17914] ppid=17912 vsize=5604 CPUtime=0.41
/proc/17914/stat : 17914 (mmisat) R 17912 17914 17638 0 -1 4195840 1351 0 0 0 40 1 0 0 20 0 1 0 206759697 5738496 1012 18446744073709551615 134512640 135391789 4294956720 18446744073709551615 135098577 0 0 4096 0 0 0 0 17 1 0 0
/proc/17914/statm: 1401 1012 114 214 0 1183 0
Current children cumulated CPU time (s) 0.41
Current children cumulated vsize (KiB) 5604

Child ended because it received signal 6 (SIGABRT)
Real time (s): 0.421925
CPU time (s): 0.419936
CPU user time (s): 0.400939
CPU system time (s): 0.018997
CPU usage (%): 99.5286
Max. virtual memory (cumulated for all children) (KiB): 5604

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.400939
system time used= 0.018997
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 1412
page faults= 0
swaps= 0
block input operations= 0
block output operations= 0
messages sent= 0
messages received= 0
signals received= 0
voluntary context switches= 8
involuntary context switches= 1

runsolver used 0.001999 second user time and 0.006998 second system time

The end

Launcher Data (download as text)

Begin job on node76 on Mon Feb 19 06:53:34 UTC 2007

IDJOB= 299221
IDBENCH= 20005
IDSOLVER= 108
FILE ID= node76/299221-1171868014

PBS_JOBID= 3839762

Free space on /tmp= 66650 MiB

SOLVER NAME= Mmisat 2007-02-08
BENCH NAME= HOME/pub/bench/SAT07/random/OnTreshold/3SAT/v600/unif-k3-r4.261-v600-c2556-S1104692480-03.SAT.shuffled.cnf
COMMAND LINE= /tmp/evaluation/299221-1171868014/mmisat /tmp/evaluation/299221-1171868014/instance-299221-1171868014.cnf            
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node76/watcher-299221-1171868014 -o ROOT/results/node76/solver-299221-1171868014 -C 1200 -M 1800 --output-limit 1,15  /tmp/evaluation/299221-1171868014/mmisat /tmp/evaluation/299221-1171868014/instance-299221-1171868014.cnf            

META MD5SUM SOLVER= f0471644c1818c6834832b41e70bf7e6
MD5SUM BENCH=  e1848ef5581233d7edc388a9e0c74c1a

RANDOM SEED= 271149360

TIME LIMIT= 1200 seconds
MEMORY LIMIT= 1800 MiB

Linux node76.alineos.net 2.6.9-34.ELsmp #1 SMP Thu Mar 9 06:23:23 GMT 2006 x86_64 x86_64 x86_64 GNU/Linux

/proc/cpuinfo:
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 15
model		: 4
model name	:                   Intel(R) Xeon(TM) CPU 3.00GHz
stepping	: 3
cpu MHz		: 3000.219
cache size	: 2048 KB
fpu		: yes
fpu_exception	: yes
cpuid level	: 5
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm pni monitor ds_cpl cid cx16 xtpr
bogomips	: 6006.18
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:

processor	: 1
vendor_id	: GenuineIntel
cpu family	: 15
model		: 4
model name	:                   Intel(R) Xeon(TM) CPU 3.00GHz
stepping	: 3
cpu MHz		: 3000.219
cache size	: 2048 KB
fpu		: yes
fpu_exception	: yes
cpuid level	: 5
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm pni monitor ds_cpl cid cx16 xtpr
bogomips	: 5999.41
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2055888 kB
MemFree:       1133400 kB
Buffers:         44280 kB
Cached:         781180 kB
SwapCached:       3460 kB
Active:         587728 kB
Inactive:       248272 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055888 kB
LowFree:       1133400 kB
SwapTotal:     4096564 kB
SwapFree:      4087076 kB
Dirty:            1132 kB
Writeback:           0 kB
Mapped:          15868 kB
Slab:            72864 kB
Committed_AS:   953404 kB
PageTables:       1424 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264388 kB
VmallocChunk: 536606243 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 66647 MiB

End job on node76 on Mon Feb 19 06:53:34 UTC 2007