Crashes when trying to run algorithm

Maybe this helps:

Time elapsed after 0 rounds: 0 hours, 0 minutes, 4 seconds
*** glibc detected *** ./optimizer: double free or corruption (top): 0x000000000213f010 ***
======= Backtrace: =========
/lib/x86_64-linux-gnu/libc.so.6(+0x7e626)[0x7fe630221626]
/lib/x86_64-linux-gnu/libc.so.6(fclose+0x155)[0x7fe6302112a5]
./optimizer[0x40465d]
./optimizer[0x400f8f]
./optimizer[0x40af87]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed)[0x7fe6301c476d]
./optimizer[0x400ca9]
======= Memory map: ========
00400000-00426000 r-xp 00000000 00:14 9966849 /home/iskaral/layout-optimization/Typing/optimizer
00625000-00626000 r--p 00025000 00:14 9966849 /home/iskaral/layout-optimization/Typing/optimizer
00626000-00627000 rw-p 00026000 00:14 9966849 /home/iskaral/layout-optimization/Typing/optimizer
00627000-00646000 rw-p 00000000 00:00 0
0213f000-02160000 rw-p 00000000 00:00 0 [heap]
7fe62ff8d000-7fe62ffa2000 r-xp 00000000 08:05 7471412 /lib/x86_64-linux-gnu/libgcc_s.so.1
7fe62ffa2000-7fe6301a1000 ---p 00015000 08:05 7471412 /lib/x86_64-linux-gnu/libgcc_s.so.1
7fe6301a1000-7fe6301a2000 r--p 00014000 08:05 7471412 /lib/x86_64-linux-gnu/libgcc_s.so.1
7fe6301a2000-7fe6301a3000 rw-p 00015000 08:05 7471412 /lib/x86_64-linux-gnu/libgcc_s.so.1
7fe6301a3000-7fe630356000 r-xp 00000000 08:05 7471272 /lib/x86_64-linux-gnu/libc-2.15.so
7fe630356000-7fe630555000 ---p 001b3000 08:05 7471272 /lib/x86_64-linux-gnu/libc-2.15.so
7fe630555000-7fe630559000 r--p 001b2000 08:05 7471272 /lib/x86_64-linux-gnu/libc-2.15.so
7fe630559000-7fe63055b000 rw-p 001b6000 08:05 7471272 /lib/x86_64-linux-gnu/libc-2.15.so
7fe63055b000-7fe630560000 rw-p 00000000 00:00 0
7fe630560000-7fe630659000 r-xp 00000000 08:05 7471262 /lib/x86_64-linux-gnu/libm-2.15.so
7fe630659000-7fe630858000 ---p 000f9000 08:05 7471262 /lib/x86_64-linux-gnu/libm-2.15.so
7fe630858000-7fe630859000 r--p 000f8000 08:05 7471262 /lib/x86_64-linux-gnu/libm-2.15.so
7fe630859000-7fe63085a000 rw-p 000f9000 08:05 7471262 /lib/x86_64-linux-gnu/libm-2.15.so
7fe63085a000-7fe63087c000 r-xp 00000000 08:05 7471278 /lib/x86_64-linux-gnu/ld-2.15.so
7fe630a52000-7fe630a55000 rw-p 00000000 00:00 0
7fe630a77000-7fe630a7c000 rw-p 00000000 00:00 0
7fe630a7c000-7fe630a7d000 r--p 00022000 08:05 7471278 /lib/x86_64-linux-gnu/ld-2.15.so
7fe630a7d000-7fe630a7f000 rw-p 00023000 08:05 7471278 /lib/x86_64-linux-gnu/ld-2.15.so
7fff2309d000-7fff230be000 rw-p 00000000 00:00 0 [stack]
7fff23163000-7fff23164000 r-xp 00000000 00:00 0 [vdso]
ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0 [vsyscall]
zsh: abort (core dumped) ./optimizer

I will gladly help to debug. :)

[michaeldickens]

I don't know off the top of my head what might be causing this, and it
is probably platform-specific (i.e. only on Linux). Are you familiar
with Valgrind? If so, you can use it to debug this more effectively.

On 5/11/12 10:06 AM, Iskaral wrote:

Maybe this helps:

Time elapsed after 0 rounds: 0 hours, 0 minutes, 4 seconds
*** glibc detected *** ./optimizer: double free or corruption (top): 0x000000000213f010 ***
======= Backtrace: =========
/lib/x86_64-linux-gnu/libc.so.6(+0x7e626)[0x7fe630221626]
/lib/x86_64-linux-gnu/libc.so.6(fclose+0x155)[0x7fe6302112a5]
./optimizer[0x40465d]
./optimizer[0x400f8f]
./optimizer[0x40af87]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed)[0x7fe6301c476d]
./optimizer[0x400ca9]
======= Memory map: ========
00400000-00426000 r-xp 00000000 00:14 9966849 /home/iskaral/layout-optimization/Typing/optimizer
00625000-00626000 r--p 00025000 00:14 9966849 /home/iskaral/layout-optimization/Typing/optimizer
00626000-00627000 rw-p 00026000 00:14 9966849 /home/iskaral/layout-optimization/Typing/optimizer
00627000-00646000 rw-p 00000000 00:00 0
0213f000-02160000 rw-p 00000000 00:00 0 [heap]
7fe62ff8d000-7fe62ffa2000 r-xp 00000000 08:05 7471412 /lib/x86_64-linux-gnu/libgcc_s.so.1
7fe62ffa2000-7fe6301a1000 ---p 00015000 08:05 7471412 /lib/x86_64-linux-gnu/libgcc_s.so.1
7fe6301a1000-7fe6301a2000 r--p 00014000 08:05 7471412 /lib/x86_64-linux-gnu/libgcc_s.so.1
7fe6301a2000-7fe6301a3000 rw-p 00015000 08:05 7471412 /lib/x86_64-linux-gnu/libgcc_s.so.1
7fe6301a3000-7fe630356000 r-xp 00000000 08:05 7471272 /lib/x86_64-linux-gnu/libc-2.15.so
7fe630356000-7fe630555000 ---p 001b3000 08:05 7471272 /lib/x86_64-linux-gnu/libc-2.15.so
7fe630555000-7fe630559000 r--p 001b2000 08:05 7471272 /lib/x86_64-linux-gnu/libc-2.15.so
7fe630559000-7fe63055b000 rw-p 001b6000 08:05 7471272 /lib/x86_64-linux-gnu/libc-2.15.so
7fe63055b000-7fe630560000 rw-p 00000000 00:00 0
7fe630560000-7fe630659000 r-xp 00000000 08:05 7471262 /lib/x86_64-linux-gnu/libm-2.15.so
7fe630659000-7fe630858000 ---p 000f9000 08:05 7471262 /lib/x86_64-linux-gnu/libm-2.15.so
7fe630858000-7fe630859000 r--p 000f8000 08:05 7471262 /lib/x86_64-linux-gnu/libm-2.15.so
7fe630859000-7fe63085a000 rw-p 000f9000 08:05 7471262 /lib/x86_64-linux-gnu/libm-2.15.so
7fe63085a000-7fe63087c000 r-xp 00000000 08:05 7471278 /lib/x86_64-linux-gnu/ld-2.15.so
7fe630a52000-7fe630a55000 rw-p 00000000 00:00 0
7fe630a77000-7fe630a7c000 rw-p 00000000 00:00 0
7fe630a7c000-7fe630a7d000 r--p 00022000 08:05 7471278 /lib/x86_64-linux-gnu/ld-2.15.so
7fe630a7d000-7fe630a7f000 rw-p 00023000 08:05 7471278 /lib/x86_64-linux-gnu/ld-2.15.so
7fff2309d000-7fff230be000 rw-p 00000000 00:00 0 [stack]
7fff23163000-7fff23164000 r-xp 00000000 00:00 0 [vdso]
ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0 [vsyscall]
zsh: abort (core dumped) ./optimizer

I will gladly help to debug. :)

---

Reply to this email directly or view it on GitHub:
#1

[plusInfinity]

I have the same issue. The valgrind showed that problem is in the line 79 of the cjalgorithm.c file. It seems that there is an extra fclose call. I didn't see in the program logic, so a dirty solution which works for me is deleting this line.

[michaeldickens]

If the repeated fclose() is the problem (and it looks like it could be), I made a change that should fix it. I'm right in the middle of implementing some new stuff, so if a new bug arises, that's probably why.