gecko/js
Bobby Holley 29dd20ec7d Bug 833856 - Handle errors better in EvaluateString. r=bz
This bug happens when we take the !useSandbox path. Basically, when the code
throws, we can end up with garbage in *aRetValue while still returning true
from EvaluateString. It looks like the convention is for these kind of eval
functions to return success even for invalid code, so lets just make sure we
check things a bit better.

This crashtest is kind of half-baked in the sense that it doesn't actually
crash without the rest of the patch. But the testcase here involves a lot of
undefined behavior (what ends up getting left in *aRetValue) during a call
to window.open (which spins the event loop, etc). I already sunk about half
an hour into trying to make it crash, so I'm just going to go with this for
now.
2013-01-25 11:17:40 +01:00
..
ductwork/debugger
examples
ipc Bug 752578 - Use mfbt's guard object implementation in js/ipc. r=Ms2ger 2012-12-27 11:20:22 -06:00
jsd bug 822289 - remove NS_IMPL_CYCLE_COLLECTION_CLASS and friends r=mccr8 2013-01-12 07:40:33 -05:00
public Bug 832026 - Measure JSRuntime::bumpAlloc_ in the JS memory reporter. r=sstangl. 2013-01-17 17:50:21 -08:00
src Bug 825714: Refactor JS allocation routines to enable allocation on parallel 2013-01-24 21:12:44 -08:00
xpconnect Bug 833856 - Handle errors better in EvaluateString. r=bz 2013-01-25 11:17:40 +01:00