ENIGMA Forums
General fluff => Announcements => Topic started by: Josh @ Dreamland on June 22, 2010, 12:42:38 pm
-
valgrind: the 'impossible' happened:
Killed by fatal signal
==28927== at 0x3809D201: myvprintf_str (m_debuglog.c:530)
==28927== by 0x3809D9E2: vgPlain_debugLog_vprintf (m_debuglog.c:877)
==28927== by 0x380298E5: vprintf_WRK (m_libcprint.c:111)
==28927== by 0x380299A7: vgPlain_printf (m_libcprint.c:143)
==28927== by 0x38027A96: vgPlain_assert_fail (m_libcassert.c:259)
==28927== by 0x74206572: ???
sched status:
running_tid=1
Thread 1: status = VgTs_Runnable
==28927== at 0x4025016: realloc (vg_replace_malloc.c:525)
==28927== by 0x80522C8: lua_table<int>::operator[](unsigned int) (lua_table.h:124)
==28927== by 0x805197D: main (var4.cpp:375)
*beats chest like an ape*
*returns to looking for the problem manually*
All that happened was realloc() took a shit. I'll look into why next. But this is why you've not heard updates.
Edit (three minutes later): all fixed
-
Can you translate?
-
Can you translate?
All that happened was realloc() took a shit.
-
Var4 now works flawlessly. I have forsaken copy on write in favor of demanding return-value optimization of the compiler. This means that sequential copy() destroy()s are optimized out at compile time. Because of this lovely feature, array returning will operate in O(1) despite COW not being implemented; meaning no additional overhead from the mix.
lua_table<> is now an operable container class you can include in ENIGMA.
Thanks to Valgrind, Var4 also doesn't leak a single byte.
Something about tacos.
-
RVO is my favorite.
-
I have no clue what any of that is, but something being killed from a fatal signal is meant to be bad isn't it? >.<
/me dies
-
Something about tacos.
(http://media.funlol.com/content/img/say-no-to-drugs-say-yes-to-tacos.jpg)
-
http://pastebin.com/eauCcd3Z
SADFACE >:
r269 (sorry Ism :D), recompiled ENIGMA as well. This was on win7 x64
EDIT: Oh and there were no errors or warnings when compiling ENIGMA either :S
-
Please don't say "latest revision" on the forums. We could come back in a week and still think you're experiencing the problem with the latest revision.