On Fri, Nov 20, 2009 at 18:31, Jose Iborra wrote:<br><div class="gmail_quote"><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
This is by design, -fbreak-on-exception breaks on any exception, be it captured or not, even on library code.<br></blockquote><div><br>Ah, that's what I missed. I would've guessed that it only breaks on uncaught exceptions.<br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I am not sure how readFile is implemented internally, but it probably
reads from the file until an eoferror is thrown and then captures it
gracefully.<br></blockquote><div><br>That's what I expect, too. I went fishing, but didn't find the exact spot where that happens within a few minutes.<br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
There is another debugger flag, -fbreak-on-error, which only breaks on unhandled exceptions.<br>
Is this what you want ?<br></blockquote></div><br>Probably. Now I see the difference in [1]. Thanks!<br><br>[1] <a href="http://www.haskell.org/ghc/docs/latest/html/users_guide/flag-reference.html#interactive-mode-options">http://www.haskell.org/ghc/docs/latest/html/users_guide/flag-reference.html#interactive-mode-options</a><br>
<br>Regards,<br>Sean<br></div>