49720 2010-11-18 02:24:46 -0800 [Qt] Not possible to catch C++ exception thrown from slot called from JS 2014-04-24 16:45:19 -0700 1 1 1 Unclassified WebKit JavaScriptCore 528+ (Nightly build) All All RESOLVED INVALID Qt, QtTriaged P3 Normal --- 49725 1 kent.hansen webkit-unassigned zherczeg oldest_to_newest 310756 0 kent.hansen 2010-11-18 02:24:46 -0800 The attached application aborts with "terminate called after throwing an instance of 'int'" even though the call to evaluateJavaScript() (which calls the slot that throws the exception) is inside a try..catch. Last tested against r72178. This only happens when the JIT is enabled. It seems the C++ runtime is not able to properly unwind the stack and find the exception handler in that case. The question is whether this is something that can be fixed in the JIT. If not, it seems like we need to introduce try..catch in the QtWebKit bridge (and convert the C++ exception to a JS exception, possibly). Alternatively, we can document that throwing exceptions from C++ is not supported in this case (e.g. the application developer should introduce try..catch on his side where necessary). 310763 1 74221 kent.hansen 2010-11-18 02:57:54 -0800 Created attachment 74221 Testcase 310766 2 kent.hansen 2010-11-18 03:17:19 -0800 Found the same issue in relation to LLVM: http://old.nabble.com/C%2B%2B-Exception-Handling-Problem-td22427938.html Solution from above thread: "My guess here is that there are JITted functions in your stack. If that's the case, you need to set the ExceptionHandling flag of LLVM on. This will make the JIT generate dwarf tables for JITted code, and libgcc will be able to unwind these functions." So the ideal solution for us would be to have dwarf table generation in JSC (that would have to be explicitly enabled, e.g. through a QWebSettings flag). 975157 3 jturcotte 2014-02-03 03:16:59 -0800 === Bulk closing of Qt bugs === If you believe that this bug report is still relevant for a non-Qt port of webkit.org, please re-open it and remove [Qt] from the summary. If you believe that this is still an important QtWebKit bug, please fill a new report at https://bugreports.qt-project.org and add a link to this issue. See http://qt-project.org/wiki/ReportingBugsInQt for additional guidelines. 1003852 4 darin 2014-04-24 16:45:19 -0700 Moving all JavaScriptGlue bugs to JavaScriptCore. The JavaScriptGlue framework itself is long gone. And most of the more recent bugs put in this component were put there by people who thought this was for some other aspect of “JavaScript glue” and have nothing to do with the actual original reason for the existence of this component, which was an OS-X-only framework named JavaScriptGlue. 74221 2010-11-18 02:57:54 -0800 2010-11-18 02:57:54 -0800 Testcase main.cpp text/x-c++src 519 kent.hansen I2luY2x1ZGUgPFF0R3VpPgojaW5jbHVkZSA8UXRXZWJLaXQ+CgpjbGFzcyBUZXN0IDogcHVibGlj IFFPYmplY3QKewogICAgUV9PQkpFQ1QKcHVibGljIHNsb3RzOgogICAgdm9pZCB0aHJvd0Zyb21D cHAoKSB7CiAgICAgICAgdGhyb3cgMTIzOwogICAgfQp9OwoKaW50IG1haW4oaW50IGFyZ2MsIGNo YXIgKiphcmd2KQp7CiAgICBRQXBwbGljYXRpb24gYXBwKGFyZ2MsIGFyZ3YpOwogICAgUVdlYlBh Z2UgcGFnZTsKICAgIFFXZWJGcmFtZSAqZnJhbWUgPSBwYWdlLm1haW5GcmFtZSgpOwogICAgVGVz dCB0c3Q7CiAgICBmcmFtZS0+YWRkVG9KYXZhU2NyaXB0V2luZG93T2JqZWN0KCJ0c3QiLCAmdHN0 KTsKICAgIHRyeSB7CiAgICAgICAgZnJhbWUtPmV2YWx1YXRlSmF2YVNjcmlwdCgidHN0LnRocm93 RnJvbUNwcCgpIik7CiAgICB9IGNhdGNoICguLi4pIHsKICAgICAgICBxV2FybmluZygiUEFTUzog Y2F1Z2h0IGV4Y2VwdGlvbiIpOwogICAgfQogICAgcmV0dXJuIDA7Cn0KCiNpbmNsdWRlICJtYWlu Lm1vYyIK