<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On Jun 4, 2012, at 5:29 AM, Broes De Cat wrote:</div><blockquote type="cite"><div class="gmail_quote">On 4 June 2012 11:49, Anton Korobeynikov <span dir="ltr"><<a href="mailto:anton@korobeynikov.info" target="_blank">anton@korobeynikov.info</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; position: static; z-index: auto; ">
Hello<br>
<div class="im"><br>
> When using clang++ 3.1 to compile our project, none of the exceptions thrown<br>
> in execute gets caught (which are IdpExceptions), instead the executable is<br>
> terminated each time with an uncaught exception.<br>
</div>It's hard to tell until you at least specify the platform you're checking.<br></blockquote><div> The platform Linux.</div></div></blockquote><div><br></div>Please be more specific. What distribution, what version of it, and (most importantly) what architecture?</div><div><br><blockquote type="cite"><div class="gmail_quote"><div>Some more testing showed the issue is more specific:</div><div>Given the stack</div>
<div>c++ code</div><div>c code</div><div>c++ code</div><div><br></div><div>An expection thrown by the highest block c++ code is not code by the lowest c++ block but instead goes straight into terminating the program.</div>
<div>(the c code is the lua library)</div></div></blockquote><div><br></div>Is clang compiling the C code? The most obvious option is that we're not compiling that code with the tables necessary to unwind through it. Does it work if you add -fexceptions or -munwind-tables to your CFLAGS?</div><div><br></div><div>John.</div></body></html>