http://marcotmarcot.wordpress.com/2010/07/21/immix-on-ghc-summer-of-code-weekly-report-10/ Thu, 27 Oct 2011 14:34:27 +0000 hourly 1 http://wordpress.com/ http://marcotmarcot.wordpress.com/2010/07/21/immix-on-ghc-summer-of-code-weekly-report-10/#comment-173 Fri, 13 Aug 2010 23:02:26 +0000 http://marcotmarcot.wordpress.com/?p=144#comment-173 [...] because, as Immix was not activated, they were not causing any harm. Now, with everything in the stage I was before: a memory corruption that happens ocasionaly only in the nofib/real/maillist benchmark. As [...]

]]> http://marcotmarcot.wordpress.com/2010/07/21/immix-on-ghc-summer-of-code-weekly-report-10/#comment-165 Wed, 11 Aug 2010 02:42:52 +0000 http://marcotmarcot.wordpress.com/?p=144#comment-165 [...] Blog do Marcot « Immix on GHC Summer of Code weekly report #10 [...]

]]> http://marcotmarcot.wordpress.com/2010/07/21/immix-on-ghc-summer-of-code-weekly-report-10/#comment-163 Tue, 10 Aug 2010 00:33:16 +0000 http://marcotmarcot.wordpress.com/?p=144#comment-163 Yes, but got nothing useful. I mentioned this on http://marcotmarcot.wordpress.com/2010/06/29/immix-on-ghc-summer-of-code-weekly-report-7/#comment-108 .

]]> http://marcotmarcot.wordpress.com/2010/07/21/immix-on-ghc-summer-of-code-weekly-report-10/#comment-159 Wed, 04 Aug 2010 12:33:01 +0000 http://marcotmarcot.wordpress.com/?p=144#comment-159 Did you try using some memory checker, i.e, valgrind, to see if you are not getting your program in any inconsistent state?

]]> http://marcotmarcot.wordpress.com/2010/07/21/immix-on-ghc-summer-of-code-weekly-report-10/#comment-148 Wed, 21 Jul 2010 16:14:52 +0000 http://marcotmarcot.wordpress.com/?p=144#comment-148 There’s also a cute name for it: heisenbug.

]]> http://marcotmarcot.wordpress.com/2010/07/21/immix-on-ghc-summer-of-code-weekly-report-10/#comment-146 Wed, 21 Jul 2010 12:45:54 +0000 http://marcotmarcot.wordpress.com/?p=144#comment-146 When attempts to add debugging code make the problem go away, it’s sometimes a signature of a compiler error.

]]>