62897 2011-06-17 11:58:33 -0700 Using "throw" with a string doesn't result in url and line number being set in the exception. 2012-09-07 00:39:57 -0700 1 1 1 Unclassified WebKit JavaScriptCore 528+ (Nightly build) All All RESOLVED DUPLICATE 18855 P2 Normal --- 1 levin webkit-unassigned barraclough ggaren levin oliver oldest_to_newest 422804 0 levin 2011-06-17 11:58:33 -0700 I guess that there is a missing call to addErrorInfo somewhere. Here's a test case: <html> <body> This should result in a one line of output with a message, url and line number. <div id=result></div> <script type="text/javascript" language="javascript"> if (window.layoutTestController) { layoutTestController.dumpAsText(); layoutTestController.waitUntilDone(); } function log(message) { document.getElementById("result").innerHTML += message + "<br>"; } window.onerror = function(msg, url, line) { // Clean up url here to remove path. log( "msg " + msg + " url " + url + " line " + line ); if (window.layoutTestController) layoutTestController.notifyDone(); } throw "Test Error"; </script> </body> </html> 422811 1 oliver 2011-06-17 12:07:03 -0700 (In reply to comment #0) > I guess that there is a missing call to addErrorInfo somewhere. > Nope, you can't add properties to a string - strings aren't objects. This is a known (and sad making limitation in JSC, and there is a bug about it, but i can't find it :-/ ) 422812 2 ggaren 2011-06-17 12:08:43 -0700 Seems like we could replace a thrown string with a string object, or a generic error object used to wrap primitive values. 422824 3 oliver 2011-06-17 12:20:22 -0700 (In reply to comment #2) > Seems like we could replace a thrown string with a string object, or a generic error object used to wrap primitive values. That would be behavioural bug -- if you throw a string, the caught value remains a string. We really just need to have an out of band mechanism for reporting where an exception came from. 422832 4 ggaren 2011-06-17 12:45:54 -0700 (In reply to comment #3) > (In reply to comment #2) > > Seems like we could replace a thrown string with a string object, or a generic error object used to wrap primitive values. > > That would be behavioural bug -- if you throw a string, the caught value remains a string. We really just need to have an out of band mechanism for reporting where an exception came from. We can distinguish between the value we pass to a catch block and the value we propagate as an exception. For example, in the generic error object design, we would unwrap the wrapped exception before running a catch block. 714218 5 barraclough 2012-09-07 00:39:57 -0700 *** This bug has been marked as a duplicate of bug 18855 ***