Trace number 1726274

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
hybridGM7 7Signal 0.12598 0.126871

General information on the benchmark

Namecrafted/Medium/contest05/jarvisalo/
mod2-3cage-unsat-9-14.sat05-2589.reshuffled-07.cnf
MD5SUM4e736dbc376aed9798860699ef195d83
Bench CategoryCRAFTED (crafted instances)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark0.000999
Satisfiable
(Un)Satisfiability was proved
Number of variables87
Number of clauses232
Sum of the clauses size696
Maximum clause length3
Minimum clause length3
Number of clauses of size 10
Number of clauses of size 20
Number of clauses of size 3232
Number of clauses of size 40
Number of clauses of size 50
Number of clauses of size over 50

Solver Data 

0.00/0.02	c Heuristic: AdaptG2WSAT 
0.00/0.02	c Hybrid barrier : 1 
0.00/0.02	c Problem instance: numAtoms = 87, numClauses = 232, numLiterals = 696
0.00/0.02	c General parameters: seed=1600799270, cutoff=1000000000, targetCost = 0, print solution: yes
0.00/0.02	c gNovelty+ parameters: noise = 0, walkprob = 1, smoothprob = 33
0.00/0.02	c tries = 1
0.00/0.02	c 
0.00/0.03	*** glibc detected *** HOME/hybridGM7: double free or corruption (out): 0x17cbd040 ***
0.00/0.03	======= Backtrace: =========
0.00/0.03	[0x8074c6e]
0.00/0.03	[0x8076ac6]
0.00/0.03	[0x804c808]
0.00/0.03	[0x80585d1]
0.00/0.03	[0x805631e]
0.00/0.03	[0x804e93b]
0.00/0.03	[0x8051262]
0.00/0.03	[0x80663da]
0.00/0.03	[0x8048171]
0.00/0.03	======= Memory map: ========
0.00/0.03	08048000-080f1000 r-xp 00000000 08:05 1835011                            HOME/hybridGM7
0.00/0.03	080f1000-080f2000 rwxp 000a9000 08:05 1835011                            HOME/hybridGM7
0.00/0.03	080f2000-17cdb000 rwxp 080f2000 00:00 0 
0.00/0.03	f7700000-f7722000 rwxp f7700000 00:00 0 
0.00/0.03	f7722000-f7800000 ---p f7722000 00:00 0 
0.00/0.03	f785b000-f7ffe000 rwxp f785b000 00:00 0 
0.00/0.03	ffe14000-ffffe000 rw-p ffe14000 00:00 0 
0.00/0.03	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-1726274-1240710359/watcher-1726274-1240710359 -o /tmp/evaluation-result-1726274-1240710359/solver-1726274-1240710359 -C 1200 -W 1800 -M 1800 --output-limit 1,15 HOME/hybridGM7 HOME/instance-1726274-1240710359.cnf 1600799270 

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.83 1.82 1.44 2/64 27237
/proc/meminfo: memFree=1782464/2055924 swapFree=4180784/4192956
[pid=27237] ppid=27235 vsize=260600 CPUtime=0
/proc/27237/stat : 27237 (hybridGM7) R 27235 27237 26913 0 -1 4194304 884 0 0 0 0 0 0 0 18 0 1 0 99070302 266854400 868 1992294400 134512640 135204385 4294956208 18446744073709551615 134542712 0 0 4096 0 0 0 0 17 1 0 0
/proc/27237/statm: 65150 875 55 168 0 64980 0

[startup+0.076046 s]
/proc/loadavg: 1.83 1.82 1.44 2/64 27237
/proc/meminfo: memFree=1782464/2055924 swapFree=4180784/4192956
[pid=27237] ppid=27235 vsize=269440 CPUtime=0.06
/proc/27237/stat : 27237 (hybridGM7) R 27235 27237 26913 0 -1 4195840 8318 0 0 0 1 5 0 0 18 0 1 0 99070302 275906560 4555 1992294400 134512640 135204385 4294956208 18446744073709551615 134788016 0 0 4096 0 0 0 0 17 1 0 0
/proc/27237/statm: 67360 4555 98 168 0 67190 0
Current children cumulated CPU time (s) 0.06
Current children cumulated vsize (KiB) 269440

[startup+0.101051 s]
/proc/loadavg: 1.83 1.82 1.44 2/64 27237
/proc/meminfo: memFree=1782464/2055924 swapFree=4180784/4192956
[pid=27237] ppid=27235 vsize=269440 CPUtime=0.09
/proc/27237/stat : 27237 (hybridGM7) R 27235 27237 26913 0 -1 4195840 8318 0 0 0 1 8 0 0 18 0 1 0 99070302 275906560 4555 1992294400 134512640 135204385 4294956208 18446744073709551615 134788016 0 0 4096 0 0 0 0 17 1 0 0
/proc/27237/statm: 67360 4555 98 168 0 67190 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 269440

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.126871
CPU time (s): 0.12598
CPU user time (s): 0.016997
CPU system time (s): 0.108983
CPU usage (%): 99.2977
Max. virtual memory (cumulated for all children) (KiB): 269440

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.016997
system time used= 0.108983
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 16908
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.005999 second user time and 0.002999 second system time

The end

Launcher Data 

Begin job on node6 at 2009-04-26 03:45:59
IDJOB=1726274
IDBENCH=24609
IDSOLVER=535
FILE ID=node6/1726274-1240710359
PBS_JOBID= 9186809
Free space on /tmp= 66336 MiB

SOLVER NAME= hybridGM7 7
BENCH NAME= SAT07/crafted/Medium/contest05/jarvisalo/mod2-3cage-unsat-9-14.sat05-2589.reshuffled-07.cnf
COMMAND LINE= HOME/hybridGM7 BENCHNAME RANDOMSEED 
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-1726274-1240710359/watcher-1726274-1240710359 -o /tmp/evaluation-result-1726274-1240710359/solver-1726274-1240710359 -C 1200 -W 1800 -M 1800 --output-limit 1,15  HOME/hybridGM7 HOME/instance-1726274-1240710359.cnf 1600799270 

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

MD5SUM BENCH= 4e736dbc376aed9798860699ef195d83
RANDOM SEED=1600799270

node6.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.281
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.281
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:      2055924 kB
MemFree:       1782944 kB
Buffers:         36804 kB
Cached:         165184 kB
SwapCached:       5956 kB
Active:          61988 kB
Inactive:       148360 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055924 kB
LowFree:       1782944 kB
SwapTotal:     4192956 kB
SwapFree:      4180784 kB
Dirty:            1116 kB
Writeback:           0 kB
Mapped:          14076 kB
Slab:            48664 kB
Committed_AS:   415320 kB
PageTables:       1452 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= 66316 MiB
End job on node6 at 2009-04-26 03:46:00