summaryrefslogtreecommitdiff
path: root/installed-tests/debugger-test.sh
Commit message (Collapse)AuthorAgeFilesLines
* test: Fix debugger test script to print diff properlyPhilip Chimento2020-11-301-4/+5
| | | | | | | | | | | | We added this test for the exit code because the tests weren't failing if one of the commands earlier in the pipeline failed, but mistakenly suppressed printing a diff of the output (because diff always "fails" if there is a difference.) If there is a diff, print it; only if there is no diff, look at the exit code. Unreviewed, pushing to make developing the debugger easier.
* maint: Add copyright notices based on major file contributorsPhilip Chimento2020-11-301-0/+1
| | | | | | | | | | | | Based on looking at the git logs, add copyright notices to files which were missing them, assuming the copyright belongs to people who made major contributions to each file. Some assumptions were made as to who to assign the copyright to, such as, what copyright assignment did the contributor make in other files added in the same commit? What email address did they use to make the commit? What copyright assignment did they make in other commits using the same email address?
* maint: Add dual MIT/LGPL license to all GJS files that didn't have onePhilip Chimento2020-10-041-0/+1
| | | | | | This adds a SPDX-License-Identifier comment to all files that are part of GJS, part of its unit tests, or auxiliary tools. (Except for some files like the debugger scripts that don't support comments.)
* installed-tests: Don't hardcode the path of bashTing-Wei Lan2019-12-011-1/+1
| | | | | This script does not contain bashism and it can be safely changed to use the default shell. This fixes 'ninja test' on FreeBSD.
* tests: Fail debugger tests if command failedPhilip Chimento2019-10-091-0/+5
| | | | | | This command fails, for example, if /usr/bin/diff is not installed. If that's the case then the test should fail, rather than passing with an error message which could be overlooked.
* debugger: GJS DebuggerPhilip Chimento2018-07-221-0/+23
This adds a simple debugger, adapted from the "jorendb" program in the SpiderMonkey source. It has basic stepping, breaking, and printing commands, that work like GDB. Activate it by running the GJS console interpreter with the -d or --debugger flag _before_ the name of the JS program on the command line. To integrate it into programs that embed the GJS interpreter, call gjs_context_setup_debugger_console() before executing the JS program. It will print when Promises are launched and resolved, although it's not yet possible to break at those points. Closes: #110
View Lorry Controller Status