Trace number 1718303

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. The first timestamp (if present) is estimated CPU time. The last timestamp is wall clock 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
march_nn nnSignal 0.12398 0.124168

General information on the benchmark

Nameindustrial/jarvisalo/
eq.atree.braun.10.unsat.cnf
MD5SUMb1a6497b6934405ef70bfcc51fa85893
Bench CategoryAPPLICATION (applications instances)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark362.542
Satisfiable
(Un)Satisfiability was proved
Number of variables1111
Number of clauses3756
Sum of the clauses size9786
Maximum clause length19
Minimum clause length1
Number of clauses of size 13
Number of clauses of size 21603
Number of clauses of size 32090
Number of clauses of size 430
Number of clauses of size 518
Number of clauses of size over 512

Solver Data 

0.00/0.03	c main():: ***                                   [ march satisfiability solver ]                                   ***
0.00/0.03	c main()::  **                Copyright (C) 2001-2009 M.J.H. Heule, J.E. van Zwieten, and M. Dufour                 **
0.00/0.03	c main()::   *  This program may be redistributed and/or modified under the terms of the GNU Gereral Public License  *
0.00/0.03	c main()::
0.00/0.03	c initFormula():: searching for DIMACS p-line....
0.00/0.03	c initFormula():: the DIMACS p-line indicates a CNF of 1111 variables and 3756 clauses.
0.00/0.03	c parseCNF():: parsing....
0.00/0.03	c parseCNF():: the CNF contains 3 unary clauses.
0.00/0.03	c runParser():: parsing was successful, warming up engines...
0.00/0.03	c simplify_formula():: removed 0 tautological, 41 satisfied and 0 duplicate clauses
0.00/0.03	c preprocessing fase I completed:: there are now 1108 free variables and 3715 clauses.
0.00/0.03	c stat :: sign balance is biased by 0.085
0.00/0.03	c find_equivalence():: found 353 3-equivalences
0.00/0.03	c find_and_remove_tautogolies():: found and removed 35 tautologies
0.00/0.03	c shorten_equivalence(): average equivalence length reduced from 6.391167 to 3.451104
0.00/0.03	c using k-SAT heuristics (size based diff)
0.00/0.03	c simplify_formula():: removed 0 tautological, 1412 satisfied and 0 duplicate clauses
0.00/0.03	c simplify_formula():: removed 0 tautological, 0 satisfied and 0 duplicate clauses
0.00/0.03	c main():: clause / variable ratio: ( 2303 / 1111 ) = 2.07
0.00/0.03	c longest clause has size 17
0.00/0.03	c simplify_formula():: removed 0 tautological, 0 satisfied and 0 duplicate clauses
0.00/0.03	c number of free variables = 1072
0.00/0.03	c dynamic_preselect_setsize :: off
0.00/0.03	c main():: all systems go!
0.00/0.03	c |----------------------------------------------------------------|*** glibc detected *** HOME/march_nn: realloc(): invalid next size: 0x0823a480 ***
0.09/0.11	======= Backtrace: =========
0.09/0.11	[0x80724be]
0.09/0.11	[0x8075d85]
0.09/0.11	[0x80769fb]
0.09/0.11	[0x804aa92]
0.09/0.11	[0x805ebfc]
0.09/0.11	[0x805f29c]
0.09/0.11	[0x805edff]
0.09/0.11	[0x805f29c]
0.09/0.11	[0x805edff]
0.09/0.11	[0x805f29c]
0.09/0.11	[0x805edff]
0.09/0.11	[0x805f29c]
0.09/0.11	[0x805edff]
0.09/0.11	[0x805f29c]
0.09/0.11	[0x805edff]
0.09/0.11	[0x805f29c]
0.09/0.11	[0x805edff]
0.09/0.11	[0x805f29c]
0.09/0.11	[0x805edff]
0.09/0.11	[0x805f29c]
0.09/0.11	[0x805edff]
0.09/0.11	[0x805f29c]
0.09/0.11	[0x805edff]
0.09/0.11	[0x805f29c]
0.09/0.11	[0x805edff]
0.09/0.11	[0x805f29c]
0.09/0.11	[0x805edff]
0.09/0.11	[0x805f29c]
0.09/0.11	[0x805edff]
0.09/0.11	[0x805f29c]
0.09/0.11	[0x805edff]
0.09/0.11	[0x805f29c]
0.09/0.11	[0x805edff]
0.09/0.11	[0x805f2ed]
0.09/0.11	[0x805344d]
0.09/0.11	[0x806462a]
0.09/0.11	[0x8048171]
0.09/0.11	======= Memory map: ========
0.09/0.11	08048000-080f0000 r-xp 00000000 08:05 5537795                            HOME/march_nn
0.09/0.11	080f0000-080f1000 rwxp 000a7000 08:05 5537795                            HOME/march_nn
0.09/0.11	080f1000-08251000 rwxp 080f1000 00:00 0 
0.09/0.11	f7e00000-f7e22000 rwxp f7e00000 00:00 0 
0.09/0.11	f7e22000-f7f00000 ---p f7e22000 00:00 0 
0.09/0.11	f7f23000-f7ffe000 rwxp f7f23000 00:00 0 
0.09/0.11	ffffa000-ffffe000 rw-p ffffa000 00:00 0 
0.09/0.11	ffffe000-fffff000 ---p 00000000 00:00 0

Verifier Data 

ERROR: Unexpected answer ! (SATISFIABLE/UNSATISFIABLE expected)
Got answer: <no 's ' line found>

Watcher Data 

runsolver version 3.2.9 (svn:492) (c) roussel@cril.univ-artois.fr

command line: BIN/runsolver --timestamp -w /tmp/evaluation-result-1718303-1240635464/watcher-1718303-1240635464 -o /tmp/evaluation-result-1718303-1240635464/solver-1718303-1240635464 -C 1200 -W 1800 -M 1800 --output-limit 1,15 HOME/march_nn HOME/instance-1718303-1240635464.cnf 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 1200 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 1230 seconds
Enforcing wall clock limit (soft limit, will send SIGTERM then SIGKILL): 1800 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.00 1.00 2/64 16766
/proc/meminfo: memFree=870680/2055920 swapFree=4192956/4192956
[pid=16766] ppid=16764 vsize=968 CPUtime=0
/proc/16766/stat : 16766 (march_nn) R 16764 16766 16645 0 -1 4194304 118 0 0 0 0 0 0 0 18 0 1 0 91580341 991232 103 1992294400 134512640 135197250 4294956240 18446744073709551615 134718462 0 0 4096 0 0 0 0 17 1 0 0
/proc/16766/statm: 242 103 59 167 0 73 0

[startup+0.0385051 s]
/proc/loadavg: 1.00 1.00 1.00 2/64 16766
/proc/meminfo: memFree=870680/2055920 swapFree=4192956/4192956
[pid=16766] ppid=16764 vsize=2696 CPUtime=0.03
/proc/16766/stat : 16766 (march_nn) R 16764 16766 16645 0 -1 4194304 362 0 0 0 3 0 0 0 18 0 1 0 91580341 2760704 344 1992294400 134512640 135197250 4294956240 18446744073709551615 134539352 0 0 4096 0 0 0 0 17 1 0 0
/proc/16766/statm: 674 344 91 167 0 505 0
Current children cumulated CPU time (s) 0.03
Current children cumulated vsize (KiB) 2696

[startup+0.101511 s]
/proc/loadavg: 1.00 1.00 1.00 2/64 16766
/proc/meminfo: memFree=870680/2055920 swapFree=4192956/4192956
[pid=16766] ppid=16764 vsize=2828 CPUtime=0.09
/proc/16766/stat : 16766 (march_nn) R 16764 16766 16645 0 -1 4194304 388 0 0 0 9 0 0 0 18 0 1 0 91580341 2895872 370 1992294400 134512640 135197250 4294956240 18446744073709551615 134525468 0 0 4096 0 0 0 0 17 1 0 0
/proc/16766/statm: 707 370 94 167 0 538 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 2828

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

Child ended because it received signal 6 (SIGABRT)
Child dumped core
Real time (s): 0.124168
CPU time (s): 0.12398
CPU user time (s): 0.114982
CPU system time (s): 0.008998
CPU usage (%): 99.8485
Max. virtual memory (cumulated for all children) (KiB): 2828

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.114982
system time used= 0.008998
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 737
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= 2
involuntary context switches= 0

runsolver used 0.002999 second user time and 0.005999 second system time

The end

Launcher Data 

Begin job on node5 at 2009-04-25 06:57:44
IDJOB=1718303
IDBENCH=20474
IDSOLVER=522
FILE ID=node5/1718303-1240635464
PBS_JOBID= 9186416
Free space on /tmp= 66348 MiB

SOLVER NAME= march_nn nn
BENCH NAME= SAT07/industrial/jarvisalo/eq.atree.braun.10.unsat.cnf
COMMAND LINE= HOME/march_nn BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-1718303-1240635464/watcher-1718303-1240635464 -o /tmp/evaluation-result-1718303-1240635464/solver-1718303-1240635464 -C 1200 -W 1800 -M 1800 --output-limit 1,15  HOME/march_nn HOME/instance-1718303-1240635464.cnf

TIME LIMIT= 1200 seconds
MEMORY LIMIT= 1800 MiB
MAX NB THREAD= 0

MD5SUM BENCH= b1a6497b6934405ef70bfcc51fa85893
RANDOM SEED=975650922

node5.alineos.net Linux 2.6.9-22.EL.rootsmp #1 SMP Mon Oct 3 08:59:52 CEST 2005

/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.212
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	: 5914.62
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.212
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	: 5586.94
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2055920 kB
MemFree:        871096 kB
Buffers:        106816 kB
Cached:         969896 kB
SwapCached:          0 kB
Active:         165984 kB
Inactive:       924716 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:        871096 kB
SwapTotal:     4192956 kB
SwapFree:      4192956 kB
Dirty:             864 kB
Writeback:           0 kB
Mapped:          23624 kB
Slab:            80088 kB
Committed_AS:   314304 kB
PageTables:       1388 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 66348 MiB
End job on node5 at 2009-04-25 06:57:44