94149d48caa9fd4ea9ceabbde8de8498545f4f7c: Merge m-c to fx-team.
Ryan VanderMeulen <ryanvm@gmail.com> - Tue, 16 Jul 2013 16:06:46 -0400 - rev 151110
Push 1 by sledru@mozilla.com at Thu, 04 Dec 2014 17:57:20 +0000
Merge m-c to fx-team.
27272cf3e1c5d9edf3d0479e705fc3c268133cde: Bug 885417 - Have UIDs as values for profiler sidebar items; r=vporof
Anton Kovalyov <anton@mozilla.com> - Tue, 16 Jul 2013 11:41:36 -0700 - rev 151109
Push 1 by sledru@mozilla.com at Thu, 04 Dec 2014 17:57:20 +0000
Bug 885417 - Have UIDs as values for profiler sidebar items; r=vporof
4527a488d1f6c7c7fcc8fd6c1e190bd4bd946da6: Merge latest green inbound changeset and mozilla-central
Ed Morley <emorley@mozilla.com> - Wed, 17 Jul 2013 15:43:28 +0100 - rev 151108
Push 1 by sledru@mozilla.com at Thu, 04 Dec 2014 17:57:20 +0000
Merge latest green inbound changeset and mozilla-central
bf423f63b3a1f714d9bac8871504abc5b38e2bfc: Bug 885107 - Sync testharness with the latest upstream. r=Ms2ger
Masatoshi Kimura <VYV03354@nifty.ne.jp> - Wed, 17 Jul 2013 20:26:24 +0900 - rev 151107
Push 1 by sledru@mozilla.com at Thu, 04 Dec 2014 17:57:20 +0000
Bug 885107 - Sync testharness with the latest upstream. r=Ms2ger
e12c6f7d66763f5479c68833b62fb59309f43c79: Bug 885107 - Fix testharness tests outside dom/imptests. r=dbaron
Masatoshi Kimura <VYV03354@nifty.ne.jp> - Wed, 17 Jul 2013 20:26:23 +0900 - rev 151106
Push 1 by sledru@mozilla.com at Thu, 04 Dec 2014 17:57:20 +0000
Bug 885107 - Fix testharness tests outside dom/imptests. r=dbaron
d671f193a5da795f0ce9c170d20f38300c8aa43b: Bug 894601 - Fix regression in context menu activation in Android.
Eitan Isaacson <eitan@monotonous.org> - Tue, 16 Jul 2013 13:49:00 +0200 - rev 151105
Push 1 by sledru@mozilla.com at Thu, 04 Dec 2014 17:57:20 +0000
Bug 894601 - Fix regression in context menu activation in Android. Bug 894601 - Fix regression in context menu activation in Android. r=maxli
7e6eb43139f17be60b31901318c6e38e984c685e: Backed out changeset 5939320824b1 (bug 894242) "CLOSED TREE"
Carsten "Tomcat" Book <cbook@mozilla.com> - Wed, 17 Jul 2013 10:36:12 +0200 - rev 151104
Push 1 by sledru@mozilla.com at Thu, 04 Dec 2014 17:57:20 +0000
Backed out changeset 5939320824b1 (bug 894242) "CLOSED TREE"
5939320824b1b0231dba75a6c373166f5622d18f: Bug 894242 - Make C++0x/C++11 mode of gcc/clang mandatory. r=ted
Mike Hommey <mh+mozilla@glandium.org> - Wed, 17 Jul 2013 16:19:25 +0900 - rev 151103
Push 1 by sledru@mozilla.com at Thu, 04 Dec 2014 17:57:20 +0000
Bug 894242 - Make C++0x/C++11 mode of gcc/clang mandatory. r=ted
af7c55ced80b7a138f6e699278c592aa21fe9014: Backout changeset cd67ffb5ca47 (bug 883381), effectively restoring bug 877937
Mike Hommey <mh+mozilla@glandium.org> - Wed, 17 Jul 2013 16:18:46 +0900 - rev 151102
Push 1 by sledru@mozilla.com at Thu, 04 Dec 2014 17:57:20 +0000
Backout changeset cd67ffb5ca47 (bug 883381), effectively restoring bug 877937
1469a9e83e2d00ba3bf3ac6acd1a0db8c0bb9550: Bug 894240 - Fix pointer dereference in js::cli::OptionParser::extractValue. r=Waldo
Mike Hommey <mh+mozilla@glandium.org> - Wed, 17 Jul 2013 16:16:55 +0900 - rev 151101
Push 1 by sledru@mozilla.com at Thu, 04 Dec 2014 17:57:20 +0000
Bug 894240 - Fix pointer dereference in js::cli::OptionParser::extractValue. r=Waldo
d5469522e7286ad2e3fc57e9d3b943e3357dbefc: Backout 1372b813d76f (bug 891695) for suspicion of causing bustage on a CLOSED TREE
Wes Kocher <wkocher@mozilla.com> - Tue, 16 Jul 2013 20:47:17 -0700 - rev 151100
Push 1 by sledru@mozilla.com at Thu, 04 Dec 2014 17:57:20 +0000
Backout 1372b813d76f (bug 891695) for suspicion of causing bustage on a CLOSED TREE
3745b7a8bfb94b082b63bb0b0879947999bfb9f4: Bug 889714 - Remove ContextCallback junk. r=mrbkap
Bobby Holley <bobbyholley@gmail.com> - Tue, 16 Jul 2013 20:38:46 -0700 - rev 151099
Push 1 by sledru@mozilla.com at Thu, 04 Dec 2014 17:57:20 +0000
Bug 889714 - Remove ContextCallback junk. r=mrbkap There's no reason we should be doing this.
068a49936b0cfea7b3b0ebcefb1eba4120865548: Bug 889714 - Use the SafeJSContext in XPCShellEnvironment. r=mrbkap
Bobby Holley <bobbyholley@gmail.com> - Tue, 16 Jul 2013 20:38:46 -0700 - rev 151098
Push 1 by sledru@mozilla.com at Thu, 04 Dec 2014 17:57:20 +0000
Bug 889714 - Use the SafeJSContext in XPCShellEnvironment. r=mrbkap
f248cb25d4db1fe1bdd8974f6bd8040d10567579: Bug 889714 - Use SystemErrorReporter instead of ScriptErrorReporter. r=mrbkap
Bobby Holley <bobbyholley@gmail.com> - Tue, 16 Jul 2013 20:38:46 -0700 - rev 151097
Push 1 by sledru@mozilla.com at Thu, 04 Dec 2014 17:57:20 +0000
Bug 889714 - Use SystemErrorReporter instead of ScriptErrorReporter. r=mrbkap SystemErrorReporter is the new unified error reporter for everything non-dom. In particular, it's used by the SafeJSContext, which we'll be switching to here shortly.
2c76f9048c0d624b69486b5b9f167d6a177aca61: Bug 889714 - Stop manually holding onto system JSPrincipals. r=mrbkap
Bobby Holley <bobbyholley@gmail.com> - Tue, 16 Jul 2013 20:38:46 -0700 - rev 151096
Push 1 by sledru@mozilla.com at Thu, 04 Dec 2014 17:57:20 +0000
Bug 889714 - Stop manually holding onto system JSPrincipals. r=mrbkap
35039a0a3316c1acb4f2cbdbf22b183ff83de06a: Bug 889714 - Stash the XPCShellEnvironment instance on the global, rather than the cx. r=mrbkap
Bobby Holley <bobbyholley@gmail.com> - Tue, 16 Jul 2013 20:38:45 -0700 - rev 151095
Push 1 by sledru@mozilla.com at Thu, 04 Dec 2014 17:57:20 +0000
Bug 889714 - Stash the XPCShellEnvironment instance on the global, rather than the cx. r=mrbkap We need to stash it somewhere, because the shell-provided JSNatives need to access it. This solution only works for script running in the scope of the global we create. Butthat's fine here, because we only use it for load() and quit(), which only exist in the scope of that global.
fe80ac2b0e25b2365def7ea0ea1485fbf2ab1ca7: Bug 889714 - Reduce the number of places where we pull |env| off cx. r=mrbkap
Bobby Holley <bobbyholley@gmail.com> - Tue, 16 Jul 2013 20:38:45 -0700 - rev 151094
Push 1 by sledru@mozilla.com at Thu, 04 Dec 2014 17:57:20 +0000
Bug 889714 - Reduce the number of places where we pull |env| off cx. r=mrbkap
5383f9b140c0a2bc46427314b48cf3383be5d811: Bug 889714 - Remove unused ExitCode machinery. r=mrbkap
Bobby Holley <bobbyholley@gmail.com> - Tue, 16 Jul 2013 20:38:45 -0700 - rev 151093
Push 1 by sledru@mozilla.com at Thu, 04 Dec 2014 17:57:20 +0000
Bug 889714 - Remove unused ExitCode machinery. r=mrbkap This stuff is cribbed from xpcshell, where it makes sense. But it doens't really make sense in the IPC context, and doesn't appear to be used either.
d2a8922b7f55b4a157137c8be5e167d0d9eead99: Bug 889714 - Removed unused ShouldReportWarnings and ShouldCompoleOnly [sic] machinery. r=mrbkap
Bobby Holley <bobbyholley@gmail.com> - Tue, 16 Jul 2013 20:38:45 -0700 - rev 151092
Push 1 by sledru@mozilla.com at Thu, 04 Dec 2014 17:57:20 +0000
Bug 889714 - Removed unused ShouldReportWarnings and ShouldCompoleOnly [sic] machinery. r=mrbkap lol @ 'ShouldCompoleOnly'.
8167594299bdee9fe7d5511dbb07fbba3a794de2: Bug 889911 - Switch xpcshell to SystemErrorReporter with a little bit of special magic. r=mrbkap
Bobby Holley <bobbyholley@gmail.com> - Tue, 16 Jul 2013 20:38:44 -0700 - rev 151091
Push 1 by sledru@mozilla.com at Thu, 04 Dec 2014 17:57:20 +0000
Bug 889911 - Switch xpcshell to SystemErrorReporter with a little bit of special magic. r=mrbkap XPCShell currently overrides all the JSContexts whose creation it observes with its own custom error reporter. This reporter does all sorts of funny things which we try to clean up for the most part. But there are a few very intricate considerations at play. First, the old xpcshell error reporter does some mumbo jumbo with the XPCCallContext stack to try to guess whether some other code might catch the exception. This is total garbage on a number of fronts, particularly because the XPCCallContext stack has no concept of saved frame chains, nested event loops, sandbox boundaries, origin boundaries, or any of the myriad of complicating factors that determine whether or not an exception will propagate. So we get rid of it. But this causes some crazy debugger tests to fail, because they rely on an exception from uriloader/exthandler/nsHandlerService.js getting squelched, and can't handle anybody reporting errors to the console service at the particular moment of contortionism when the exception is raised. So we need to introduce an explicit mechanism to disable the error reporter here to keep things running. Second, we have to be very careful about tracking the return status of the xpcshell binary. The old code would simply flag an error code if the error handler was invoked, and we can mostly continue to do that. But there are some complications. See the comments. Finally, we don't anything analogous in XPCShellEnvironment, because I have patches in bug 889714 to remove its state-dependence on the error reporter. I'll switch it to SystemErrorReporter in that bug.
(0) -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 tip