-
-
Notifications
You must be signed in to change notification settings - Fork 851
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
avm2: Enable stack traces for Flash Player 11.5+ and SWF18+ #19571
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Despite what the docs say, this behavior also seems to depend on the SWF version. Notice that the attached SWF displays no stack trace in release FP: StackTraceTest.zip. But if you change the SWF version to 18 or higher in JPEXS, then the stack trace appears.
Also, be sure to test #12572 since it is affected by the behavior of getStackTrace().
7c4df88
to
aea9328
Compare
This option specifies whether to emulate flashplayer (release mode) or flashplayerdebugger (debug mode).
For Flash Player 11.5+ and SWF18+, stack traces are always enabled. Some content uses this behavior to verify whether the user is using Flash Player 11.5 onwards. For Flash Player 11.4 and earlier or SWF<18, stack traces are enabled only in the debug build. See <https://docs.ruffle.rs/en_US/FlashPlatform/reference/actionscript/3/Error.html#getStackTrace()>
These tests check whether stack traces are returned based on the SWF version and the debug/release mode.
aea9328
to
7eb20de
Compare
For Flash Player 11.5+ and SWF18+, stack traces are always enabled. Some content uses this behavior to verify whether the user is using Flash Player 11.5 onwards.
See https://docs.ruffle.rs/en_US/FlashPlatform/reference/actionscript/3/Error.html#getStackTrace()
Related:
Info
#10310CC @adrian17 @Lord-McSweeney