26 Apr, 2009, Malek Kervanes wrote in the 1st comment:
Votes: 0
got an issue. Running Kubuntu on a VirtualBox VM and got this when I executed my binary.

*** glibc detected *** ../game/boti2: malloc(): memory corruption: 0xb7f14008 ***
======= Backtrace: =========
/lib/tls/i686/cmov/libc.so.6[0xb7ddb356]
/lib/tls/i686/cmov/libc.so.6(__libc_malloc+0x8d)[0xb7ddccad]
/lib/tls/i686/cmov/libc.so.6[0xb7dc9d2f]
/lib/tls/i686/cmov/libc.so.6(fopen+0x2c)[0xb7dc9dfc]
../game/boti2[0x804abf4]
../game/boti2[0x804f143]
../game/boti2[0x804ed44]
../game/boti2[0x804c6d5]
/lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe0)[0xb7d85450]
../game/boti2[0x80490f1]
======= Memory map: ========
08048000-08058000 r-xp 00000000 08:01 264159 /home/wolfden/boti2/game/boti2
08058000-08059000 rw-p 00010000 08:01 264159 /home/wolfden/boti2/game/boti2
08059000-0807e000 rw-p 08059000 00:00 0 [heap]
b7c00000-b7c21000 rw-p b7c00000 00:00 0
b7c21000-b7d00000 —p b7c21000 00:00 0
b7d6e000-b7d6f000 rw-p b7d6e000 00:00 0
b7d6f000-b7eb8000 r-xp 00000000 08:01 539921 /lib/tls/i686/cmov/libc-2.7.so
b7eb8000-b7eb9000 r–p 00149000 08:01 539921 /lib/tls/i686/cmov/libc-2.7.so
b7eb9000-b7ebb000 rw-p 0014a000 08:01 539921 /lib/tls/i686/cmov/libc-2.7.so
b7ebb000-b7ebf000 rw-p b7ebb000 00:00 0
b7ebf000-b7ec8000 r-xp 00000000 08:01 539925 /lib/tls/i686/cmov/libcrypt-2.7.so
b7ec8000-b7eca000 rw-p 00008000 08:01 539925 /lib/tls/i686/cmov/libcrypt-2.7.so
b7eca000-b7ef1000 rw-p b7eca000 00:00 0
b7ef1000-b7f05000 r-xp 00000000 08:01 539947 /lib/tls/i686/cmov/libpthread-2.7.so
b7f05000-b7f07000 rw-p 00013000 08:01 539947 /lib/tls/i686/cmov/libpthread-2.7.so
b7f07000-b7f09000 rw-p b7f07000 00:00 0
b7f09000-b7f13000 r-xp 00000000 08:01 522305 /lib/libgcc_s.so.1
b7f13000-b7f14000 rw-p 0000a000 08:01 522305 /lib/libgcc_s.so.1
b7f14000-b7f19000 rw-p b7f14000 00:00 0
b7f19000-b7f1a000 r-xp b7f19000 00:00 0 [vdso]
b7f1a000-b7f34000 r-xp 00000000 08:01 522260 /lib/ld-2.7.so
b7f34000-b7f36000 rw-p 00019000 08:01 522260 /lib/ld-2.7.so
bfbdc000-bfbf1000 rw-p bffeb000 00:00 0 [stack]


Any help would be good….never seen this before
26 Apr, 2009, David Haley wrote in the 2nd comment:
Votes: 0
First thing to try: 'make clean' and 'make'
If that doesn't fix it, it's a bug in your code. Second thing to try: install valgrind and debug it. :smile:
26 Apr, 2009, Malek Kervanes wrote in the 3rd comment:
Votes: 0
yeah…was trying to catch where my code was failing and told it to write something to a logfile that it didn't have.

Just never seen it throw a memory like that before.
26 Apr, 2009, David Haley wrote in the 4th comment:
Votes: 0
Glad that you fixed the problem. BTW, normally we avoid deleting threads and content so that people can learn from the threads in the future.
26 Apr, 2009, Malek Kervanes wrote in the 5th comment:
Votes: 0
ah ok…gotcha….I'll fix the OP back to the way it was.
0.0/5