| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
Since they're only available for certain platforms, we need to
autodetect.
Reviewed-by: Kent Hansen
|
|
|
|
| |
Also build new binary.
|
|
|
|
|
| |
The options were added to the configure script (Unix/Mac) already,
so bring Windows configure in sync.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
A lot of the JSC::ExecState functions rely on scopeChain() not
being 0. This means we shouldn't pop the scope chain if doing so
would make it empty; otherwise when you call e.g. pushScope() or
evaluate(), you will crash. So instead of popping the chain
completely, we now set the sole scope chain item's object pointer to
0 and add appropriate checks elsewhere.
A second issue, not solved in this commit, is that JSC expects
the Global Object to always be the last item in every scope
chain. If it's not, you will crash.
|
|
|
|
|
|
| |
We don't need the JSC asserts anymore now, hopefully.
More importantly, this changemakes programs that link against both
QtScript and QtWebKit not crash.
|
|
|
|
|
|
|
|
|
|
| |
b62ab93d001d2f3238e24faa133720cb877e3023 commit.
Workaround for multiple decorators problem. FunctionWrapper and
NativeConstrWrapper needs access to original result value (from native
function call). Solution was to move part of the NativeConstrWrapper's
functionality (functionExit debugger's event) to
FunctionWrapper::proxyConstruct.
|
|
|
|
|
|
|
| |
b62ab93d001d2f3238e24faa133720cb877e3023 commit.
Calls to Debuggers's evaluateStart, evaluateStop, exceptionThrow methods
where created.
|
|\
| |
| |
| | |
git@scm.dev.nokia.troll.no:qt/qt-webkit into qtscript-jsc-backend
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
For arguments, we always need to skip the implicit 'this' argument
For line number, we walk thought the stack frames from the top to find
the one above the requested one, which contains the returnPC we need.
Also fixed a crash because QScriptContext::parentContext would have
returned a pointer with flags inside.
Reviewed-by: Kent Hansen
|
| | |
|
| | |
|
| | |
|
|/
|
|
|
|
|
|
|
|
|
| |
b62ab93d001d2f3238e24faa133720cb877e3023 commit.
In CallData and ConstructData native function call were replaced by
class with operator() that decorate every call with debugger->functionEntry
and debugger->functionExit events.
In Interpreter new debugger calls for functionExit, functionEntry,
exceptionThrow and exceptionCatch events where created
|
|\
| |
| |
| | |
git@scm.dev.nokia.troll.no:qt/qt-webkit into qtscript-jsc-backend
|
| |
| |
| |
| |
| | |
Also fix some autotest failures, improve the descriptions of failures,
and make the tests run to completion.
|
|/
|
|
|
|
|
| |
Setting Debugger for JSGlobalObject automatically set it to ScriptPool
object.
Should be part of f5af011ede569bb88ec9b27ff7a65fe99f7d17fd commit
|
| |
|
|\
| |
| |
| | |
git@scm.dev.nokia.troll.no:qt/qt-webkit into qtscript-jsc-backend
|
| | |
|
|/
|
|
|
|
|
| |
Generation point of debug opcode for different statements were changed
to simulate old - backend QtScript's debugger.
Code is Qt specific and secured by QT_BUILD_SCRIPT_LIB define.
|
|\
| |
| |
| | |
git@scm.dev.nokia.troll.no:qt/qt-webkit into qtscript-jsc-backend
|
| |
| |
| |
| |
| |
| |
| | |
In the JSC-based back-end, script-owned QObjects are not always
deleted immediately by the GC. I don't know what precisely
determines the deletion time yet. (Inserting a qDebug() before
evaluate("gc()") seems to fix it, though...)
|
| |
| |
| |
| |
| |
| |
| | |
SourcePool's objects should be responsible for calling debugger each time
scriptLoad or scriptUnload event occurs.
This code is specific to Qt only.
|
|\ \
| |/
| |
| | |
git@scm.dev.nokia.troll.no:qt/qt-webkit into qtscript-jsc-backend
|
| |
| |
| |
| |
| | |
Introduce a frameForContext() function so we don't have to cast
all over the place.
|
| |
| |
| |
| |
| | |
Added the properties to the activation object: __extension__,
__setupPackage__ and __postInit__.
|
| |\
| | |
| | |
| | | |
git@scm.dev.nokia.troll.no:qt/qt-webkit into qtscript-jsc-backend
|
|\ \ \
| |/ /
|/| /
| |/ |
git@scm.dev.nokia.troll.no:qt/qt-webkit into qtscript-jsc-backend
|
| |
| |
| |
| |
| | |
It's an internal function, and currently not implemented
in the JSC-based back-end.
|
|/
|
|
|
|
|
|
|
|
|
|
| |
where created:
scriptUnload, scriptLoad, contextPush, contextPop, evaluateStart,
evaluateStop, exceptionThrow, exceptionCatch, functionExit
Some of them are really similar to standard JSC events but not
enough to implement correct old QtScript debugger behavior.
Default empty implementation where created (the new events are not pure
virtual methods as the others)
|
|\
| |
| |
| | |
git@scm.dev.nokia.troll.no:qt/qt-webkit into qtscript-jsc-backend
|
| |
| |
| |
| |
| | |
QScriptContext::backtrace() is implemented now (since commit
34511e1001471ed4041794640aefe508f50ad01c), so the tests work.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
It doesn't work for overloaded methods yet (unless you just
happened to call the overload that's defined last in the source
file).
In the old back-end we stored the actual overload that was being
called in the QScriptContextPrivate. Since QScriptContext is a
JSC::ExecState now, we either have to add the information to
JSC::ExecState, or add some mapping scheme so we can go
determine the meta-index for a particular (ExecState, QtFunction)
pair.
Also in this commit: Marked expected failures, so the autotests
will run to completion.
|
|/
|
|
|
|
|
| |
opcode and pass it for DidReachBreakpoint and WillExecuteStatement
events as an argument.
Compilation fix for JIT.
|
|
|
|
|
| |
Look up the property as a normal JS property before falling back
to the dynamic query mechanism. This is the documented behavior.
|
|
|
|
|
| |
Doesn't pass the test yet, but at least it returns something that
might be useful on occasion.
|
| |
|
|
|
|
|
| |
returnValue() and setReturnValue() are internal functions not
implemented in the JSC-based back-end.
|
|
|
|
|
| |
QScriptValue::scope() and QScriptValue::setScope() are internal
function that we don't implement fully in the JSC-based back-end.
|
|
|
|
| |
Missing parentheses in function expression (JSC requires them).
|
|
|
|
| |
Accept the presence of a JSON object.
|
|
|
|
| |
QtScript defines its own print function.
|
|
|
|
|
| |
JSObject::getPropertyAttributes() does not follow the prototype
chain, so we have to do it.
|
|
|
|
|
| |
Look in the __qt_scope__ property that is set by
QScriptValue::setScope().
|
|\
| |
| |
| |
| |
| |
| |
| |
| | |
qtscript-jsc-backend
Conflicts:
src/script/api/qscriptable.cpp
src/script/api/qscriptable_p.h
src/script/qscriptclassdata.cpp
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The code block associated with QBENCHMARK_ONCE macro will only be executed once,
whether the backend returns a valid result or not. The "-iterations" command line
argument is also ignored.
This is useful for benchmarking code that has side effects.
Revby: jasplin
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The documentation implies that start restarts. Which it did, but only if the
timeline was finished _and_ the duration hadn't been changed meanwhile.
So after a setDuration(), start() would do nothing, which was unexpected.
Merge-request: 1145
Reviewed-by: Olivier Goffart <ogoffart@trolltech.com>
|
| |\ |
|
| | |
| | |
| | |
| | | |
Reviewed-by: Aaron Kennedy
|