mirror of
https://gitlab.winehq.org/wine/wine-gecko.git
synced 2024-09-13 09:24:08 -07:00
Gecko engine for Wine
08a0fc18a5
This patch makes SpiderMonkey respect resumption values returned by Debugger onEnterFrame handler functions, as documented. In Debugger, we change fireEnterFrame to collect a resumption value from the hook, and change onEnterFrame and slowPathOnEnterFrame to propagate them out. These now need an 'rval' argument, so that they can return forced return values and exceptions. ScriptDebugPrologue now accepts a JSTrapStatus from Debugger::onEnterFrame, takes care of placing the return value or exception where it belongs, and returns a JSTrapStatus. Calls to ScriptDebugPrologue now handle the JSTrapStatus: - at the head of js::Interpret; - in the JSOP_NEW/JSOP_CALL/JSOP_FUNCALL/JSOP_FUNAPPLY case; - in stubs::ScriptDebugPrologue, which JM epilogues call; and - in the REJOIN_THIS_PROTOTYPE case in js_InternalInterpret (you must add a JS_GC call to ic::GetPropNoCache for Debugger-onEnterFrame-resumption-05.js to hit this reliably). We also rearrange the js_InternalThrow JSTrapStatus-handling switch statement to have an explicit default case that raises a JS_NOT_REACHED assertion, instead of just omitting JSTRAP_CONTINUE. |
||
---|---|---|
accessible | ||
browser | ||
build | ||
caps | ||
chrome | ||
config | ||
content | ||
db/sqlite3 | ||
dbm | ||
docshell | ||
dom | ||
editor | ||
embedding | ||
extensions | ||
gfx | ||
hal | ||
image | ||
intl | ||
ipc | ||
js | ||
layout | ||
media | ||
memory | ||
mfbt | ||
mobile/xul | ||
modules | ||
netwerk | ||
nsprpub | ||
other-licenses | ||
parser | ||
probes | ||
profile | ||
rdf | ||
security | ||
services | ||
startupcache | ||
storage | ||
testing | ||
toolkit | ||
tools | ||
uriloader | ||
view | ||
widget | ||
xpcom | ||
xpfe | ||
xulrunner | ||
.gitignore | ||
.hgignore | ||
.hgtags | ||
aclocal.m4 | ||
allmakefiles.sh | ||
client.mk | ||
client.py | ||
configure.in | ||
LEGAL | ||
LICENSE | ||
Makefile.in | ||
README.txt |
An explanation of the Mozilla Source Code Directory Structure and links to project pages with documentation can be found at: https://developer.mozilla.org/en/Mozilla_Source_Code_Directory_Structure For information on how to build Mozilla from the source code, see: http://developer.mozilla.org/en/docs/Build_Documentation To have your bug fix / feature added to Mozilla, you should create a patch and submit it to Bugzilla (https://bugzilla.mozilla.org). Instructions are at: http://developer.mozilla.org/en/docs/Creating_a_patch http://developer.mozilla.org/en/docs/Getting_your_patch_in_the_tree If you have a question about developing Mozilla, and can't find the solution on http://developer.mozilla.org, you can try asking your question in a mozilla.* Usenet group, or on IRC at irc.mozilla.org. [The Mozilla news groups are accessible on Google Groups, or news.mozilla.org with a NNTP reader.] You can download nightly development builds from the Mozilla FTP server. Keep in mind that nightly builds, which are used by Mozilla developers for testing, may be buggy. Firefox nightlies, for example, can be found at: ftp://ftp.mozilla.org/pub/firefox/nightly/latest-trunk/ - or - http://nightly.mozilla.org/