On 02/16/12 03:21, Antoine Villeret wrote:
i hope thoses informations are enough to quickly fix the issue cause it freaks me out !
unfortunately not. i'm pretty sure that the revision you found with "git bisect" is totally unrelated to the problem, which might indicate some memory corruption.
would you mind using some debugging beasts, like gdb (to get a backtrace) and valgrind (to check for memory corruption)?
oh, and what OS ar you on?
fgm,asdr IOhannes