Merge lp:~aacid/unity8/enable_debugging_flag into lp:unity8
| Status: | Merged |
|---|---|
| Approved by: | Michael Zanetti on 2016-04-08 |
| Approved revision: | 2329 |
| Merged at revision: | 2358 |
| Proposed branch: | lp:~aacid/unity8/enable_debugging_flag |
| Merge into: | lp:unity8 |
| Diff against target: |
83 lines (+43/-0) 3 files modified
src/Dash/main.cpp (+5/-0) src/main.cpp (+5/-0) src/qmldebuggerutils.h (+33/-0) |
| To merge this branch: | bzr merge lp:~aacid/unity8/enable_debugging_flag |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Michael Zanetti (community) | 2016-04-05 | Approve on 2016-04-08 | |
| Unity8 CI Bot | continuous-integration | Needs Fixing on 2016-04-08 | |
|
Review via email:
|
|||
Commit Message
Add env var to enable js debugging/profiling even if not built on debug mode
Description of the Change
How to test:
* Compile with -DCMAKE_
* run builddir/
* See nothing about js debugging is printed
* run ENABLE_
* See how "QML debugging is enabled. Only use this in a safe environment." is printed
* Are there any related MPs required for this MP to build/function as expected?
No
* Did you perform an exploratory manual test run of your code change and any related functionality?
Yes
* Did you make sure that your branch does not contain spurious tags?
Yes
* If you changed the packaging (debian), did you subscribe the ubuntu-unity team to this MP?
N/A
* If you changed the UI, has there been a design review?
N/A
| Gerry Boland (gerboland) wrote : | # |
| Albert Astals Cid (aacid) wrote : | # |
> /me wonders if we should enable debugging if the -qmljsdebugger switch is set.
> One less hoop to jump through. Just a thought.
went for a new flag to make it clearer it is a different thing, i.e. otherwise you may run -qmljsdebugger on a different binary and wonder why it's not working.
This way you could still use ENABLE_QML_DEBUGGER on a different binary and wonder why it doesn't work but a grep over unity8 codebase will show why.
- 2327. By Albert Astals Cid on 2016-04-05
-
Add to unity8 too
| Unity8 CI Bot (unity8-ci-bot) wrote : | # |
FAILED: Continuous integration, rev:2326
https:/
Executed test runs:
SUCCESS: https:/
SUCCESS: https:/
FAILURE: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
Click here to trigger a rebuild:
https:/
| Unity8 CI Bot (unity8-ci-bot) wrote : | # |
FAILED: Continuous integration, rev:2327
https:/
Executed test runs:
SUCCESS: https:/
UNSTABLE: https:/
FAILURE: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
Click here to trigger a rebuild:
https:/
| Michael Zanetti (mzanetti) wrote : | # |
if the -qmljsdebugger argument is always required (as it turned out to be in my tests) then not sure we need the env variable indeed, as Gerry said. I'd also be ok with the other way round, somehow configure it to some port (preferably 3768 as that's the preselected in our IDE) so exporting the env var is good enough and -qmljsdebugger arg is not needed any more.
- 2328. By Albert Astals Cid on 2016-04-08
-
Make enabling the qml debugger depend on the -qmljsdebugger command line option being there or not
- 2329. By Albert Astals Cid on 2016-04-08
-
eof
| Unity8 CI Bot (unity8-ci-bot) wrote : | # |
FAILED: Continuous integration, rev:2328
https:/
Executed test runs:
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
FAILURE: https:/
SUCCESS: https:/
deb: https:/
FAILURE: https:/
SUCCESS: https:/
deb: https:/
FAILURE: https:/
SUCCESS: https:/
deb: https:/
Click here to trigger a rebuild:
https:/
| Unity8 CI Bot (unity8-ci-bot) wrote : | # |
FAILED: Continuous integration, rev:2329
https:/
Executed test runs:
SUCCESS: https:/
SUCCESS: https:/
UNSTABLE: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
Click here to trigger a rebuild:
https:/
| Unity8 CI Bot (unity8-ci-bot) wrote : | # |
FAILED: Continuous integration, rev:2328
https:/
Executed test runs:
SUCCESS: https:/
SUCCESS: https:/
FAILURE: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
SUCCESS: https:/
deb: https:/
Click here to trigger a rebuild:
https:/
| Michael Zanetti (mzanetti) wrote : | # |
A small nitpick perhaps... Your code accepts "--qmljsdebugger", however the qmljsdebugger only accepts it with one "-". This ends up with this message:
QML debugging is enabled. Only use this in a safe environment.
unity8-dash: unrecognized option '--qmljsdebugge
| Michael Zanetti (mzanetti) wrote : | # |
ok, turns out this is just a bogus debug print from Qt, it actually still works with -- too.
* Did you perform an exploratory manual test run of the code change and any related functionality?
yes
* Did CI run pass? If not, please explain why.
yes
* Did you make sure that the branch does not contain spurious tags?
yes

/me wonders if we should enable debugging if the -qmljsdebugger switch is set. One less hoop to jump through. Just a thought.