The Tor Browser / file comparison
comparison: js/src/gdb/lib-for-tests/catcher.py
js/src/gdb/lib-for-tests/catcher.py
- changeset 0
- 6474c204b198
equal
deleted
inserted
replaced
| -1:000000000000 | 0:1e074b3469cb |
|---|---|
| 1 # Apparently, there's simply no way to ask GDB to exit with a non-zero | |
| 2 # status when the script run with the --eval-command option fails. Thus, if | |
| 3 # we have --eval-command run prolog.py directly, syntax errors there will | |
| 4 # lead GDB to exit with no indication anything went wrong. | |
| 5 # | |
| 6 # To avert that, we use this very small launcher script to run prolog.py | |
| 7 # and catch errors. | |
| 8 # | |
| 9 # Remember, errors in this file will cause spurious passes, so keep this as | |
| 10 # simple as possible! | |
| 11 | |
| 12 import os | |
| 13 import sys | |
| 14 import traceback | |
| 15 try: | |
| 16 # testlibdir is set on the GDB command line, via: | |
| 17 # --eval-command python testlibdir=... | |
| 18 execfile(os.path.join(testlibdir, 'prolog.py')) | |
| 19 except Exception as err: | |
| 20 sys.stderr.write('Error running GDB prologue:\n') | |
| 21 traceback.print_exc() | |
| 22 sys.exit(1) |
