Trace number 1727145

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
MoRsat 2009-03-03Signal 0.485925 0.486147

General information on the benchmark

Namecrafted/Hard/contest04/others/
equilarge_l4.sat05-521.reshuffled-07.cnf
MD5SUMff36f96f6b8096039d33a91da209fed4
Bench CategoryCRAFTED (crafted instances)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark1179.17
Satisfiable
(Un)Satisfiability was proved
Number of variables4499
Number of clauses18603
Sum of the clauses size54454
Maximum clause length3
Minimum clause length2
Number of clauses of size 10
Number of clauses of size 21355
Number of clauses of size 317248
Number of clauses of size 40
Number of clauses of size 50
Number of clauses of size over 50

Solver Data 

0.00/0.00	c MoRsat version 1.02 2009.03 *** glibc detected *** HOME/MoRsat: double free or corruption (!prev): 0x0817eb48 ***
0.40/0.48	======= Backtrace: =========
0.40/0.48	[0x80d7b6e]
0.40/0.48	[0x80d99c6]
0.40/0.48	[0x805176b]
0.40/0.48	[0x8052fe4]
0.40/0.48	[0x8053353]
0.40/0.48	[0x8056a8c]
0.40/0.48	[0x804e636]
0.40/0.48	[0x80baeaa]
0.40/0.48	[0x8048171]
0.40/0.48	======= Memory map: ========
0.40/0.48	08048000-08165000 r-xp 00000000 08:05 3686403                            HOME/MoRsat
0.40/0.48	08165000-08167000 rwxp 0011d000 08:05 3686403                            HOME/MoRsat
0.40/0.48	08167000-0826a000 rwxp 08167000 00:00 0 
0.40/0.48	f7d00000-f7d24000 rwxp f7d00000 00:00 0 
0.40/0.48	f7d24000-f7e00000 ---p f7d24000 00:00 0 
0.40/0.48	f7e29000-f7e88000 rwxp f7e29000 00:00 0 
0.40/0.48	f7f8e000-f7f93000 rwxp f7f8e000 00:00 0 
0.40/0.48	f7ffd000-f7ffe000 rwxp f7ffd000 00:00 0 
0.40/0.48	ffffc000-ffffe000 rw-p ffffc000 00:00 0 
0.40/0.48	ffffe000-fffff000 ---p 00000000 00:00 0 
0.40/0.48	
0.40/0.48	c atom#=4499 clause#=18603 total literals=54454

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-1727145-1240721481/watcher-1727145-1240721481 -o /tmp/evaluation-result-1727145-1240721481/solver-1727145-1240721481 -C 1200 -W 1800 -M 1800 --output-limit 1,15 HOME/MoRsat HOME/instance-1727145-1240721481.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: 0.92 0.98 0.99 3/64 20890
/proc/meminfo: memFree=1309600/2055920 swapFree=4192812/4192956
[pid=20890] ppid=20888 vsize=1768 CPUtime=0
/proc/20890/stat : 20890 (MoRsat) R 20888 20890 20791 0 -1 4194304 137 0 0 0 0 0 0 0 18 0 1 0 100175285 1810432 121 1992294400 134512640 135679800 4294956240 18446744073709551615 135172366 0 0 4096 1026 0 0 0 17 1 0 0
/proc/20890/statm: 442 122 96 284 0 155 0

[startup+0.010384 s]
/proc/loadavg: 0.92 0.98 0.99 3/64 20890
/proc/meminfo: memFree=1309600/2055920 swapFree=4192812/4192956
[pid=20890] ppid=20888 vsize=1768 CPUtime=0
/proc/20890/stat : 20890 (MoRsat) R 20888 20890 20791 0 -1 4194304 154 0 0 0 0 0 0 0 18 0 1 0 100175285 1810432 138 1992294400 134512640 135679800 4294956240 18446744073709551615 135172366 0 0 4096 1026 0 0 0 17 1 0 0
/proc/20890/statm: 442 139 96 284 0 155 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 1768

[startup+0.102391 s]
/proc/loadavg: 0.92 0.98 0.99 3/64 20890
/proc/meminfo: memFree=1309600/2055920 swapFree=4192812/4192956
[pid=20890] ppid=20888 vsize=2160 CPUtime=0.1
/proc/20890/stat : 20890 (MoRsat) R 20888 20890 20791 0 -1 4194304 425 0 0 0 10 0 0 0 18 0 1 0 100175285 2211840 353 1992294400 134512640 135679800 4294956240 18446744073709551615 134567872 0 0 4096 1026 0 0 0 17 1 0 0
/proc/20890/statm: 540 353 106 284 0 253 0
Current children cumulated CPU time (s) 0.1
Current children cumulated vsize (KiB) 2160

[startup+0.302407 s]
/proc/loadavg: 0.92 0.98 0.99 3/64 20890
/proc/meminfo: memFree=1309600/2055920 swapFree=4192812/4192956
[pid=20890] ppid=20888 vsize=3816 CPUtime=0.3
/proc/20890/stat : 20890 (MoRsat) R 20888 20890 20791 0 -1 4194304 505 0 0 0 30 0 0 0 19 0 1 0 100175285 3907584 322 1992294400 134512640 135679800 4294956240 18446744073709551615 134547510 0 0 4096 1026 0 0 0 17 1 0 0
/proc/20890/statm: 954 322 108 284 0 667 0
Current children cumulated CPU time (s) 0.3
Current children cumulated vsize (KiB) 3816

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

[startup+0.402416 s]
/proc/loadavg: 0.92 0.98 0.99 3/64 20890
/proc/meminfo: memFree=1309600/2055920 swapFree=4192812/4192956
[pid=20890] ppid=20888 vsize=3816 CPUtime=0.4
/proc/20890/stat : 20890 (MoRsat) R 20888 20890 20791 0 -1 4194304 531 0 0 0 40 0 0 0 20 0 1 0 100175285 3907584 348 1992294400 134512640 135679800 4294956240 18446744073709551615 134547418 0 0 4096 1026 0 0 0 17 1 0 0
/proc/20890/statm: 954 348 108 284 0 667 0
Current children cumulated CPU time (s) 0.4
Current children cumulated vsize (KiB) 3816

Child ended because it received signal 6 (SIGABRT)
Child dumped core
Real time (s): 0.486147
CPU time (s): 0.485925
CPU user time (s): 0.480926
CPU system time (s): 0.004999
CPU usage (%): 99.9544
Max. virtual memory (cumulated for all children) (KiB): 3816

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.480926
system time used= 0.004999
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 727
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= 2

runsolver used 0.003999 second user time and 0.004999 second system time

The end

Launcher Data 

Begin job on node58 at 2009-04-26 06:51:21
IDJOB=1727145
IDBENCH=24631
IDSOLVER=502
FILE ID=node58/1727145-1240721481
PBS_JOBID= 9186896
Free space on /tmp= 65940 MiB

SOLVER NAME= MoRsat 2009-03-03
BENCH NAME= SAT07/crafted/Hard/contest04/others/equilarge_l4.sat05-521.reshuffled-07.cnf
COMMAND LINE= HOME/MoRsat BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-1727145-1240721481/watcher-1727145-1240721481 -o /tmp/evaluation-result-1727145-1240721481/solver-1727145-1240721481 -C 1200 -W 1800 -M 1800 --output-limit 1,15  HOME/MoRsat HOME/instance-1727145-1240721481.cnf

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

MD5SUM BENCH= ff36f96f6b8096039d33a91da209fed4
RANDOM SEED=2009512517

node58.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.233
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.233
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:       1310016 kB
Buffers:         48864 kB
Cached:         613992 kB
SwapCached:        144 kB
Active:         160496 kB
Inactive:       516452 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1310016 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            1716 kB
Writeback:           0 kB
Mapped:          23680 kB
Slab:            54964 kB
Committed_AS:   355480 kB
PageTables:       1356 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= 65940 MiB
End job on node58 at 2009-04-26 06:51:21