<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On 14 Mar 2013, at 11:16, Tomas Hajny wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Monaco; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="Apple-style-span" style="font-family: monospace; ">On Thu, March 14, 2013 09:23, Xiangrong Fang wrote:<br><blockquote type="cite"><br></blockquote><blockquote type="cite">I am sorry that was what I thought, but does not work, see screenshot<br></blockquote><blockquote type="cite">attached.<br></blockquote><br>The screenshot does not show where exactly the problem happens (except for<br>the address, but that is useless without context), i.e. if it is covered<br>by the try..except construct.</span></span></blockquote></div><br><div>Indeed, it probably crashes in FreeMemory or fs.free because the heap manager structures have been corrupted. The fs.Read itself does not necessarily raise an exception by itself in case there's still enough room in the heap block that contains buf, or if another one comes right after it.</div><div><br></div><div><br></div><div>Jonas</div></body></html>