Closed Bug 515844 Opened 15 years ago Closed 15 years ago

TM: trace-test.py: option to run test case in debugger

Categories

(Core :: JavaScript Engine, enhancement)

enhancement
Not set
normal

Tracking

()

RESOLVED FIXED
Tracking Status
status1.9.2 --- beta1-fixed

People

(Reporter: dmandelin, Assigned: dmandelin)

Details

(Whiteboard: fixed-in-tracemonkey)

Attachments

(1 file)

Attached patch PatchSplinter Review
By popular demand. To run the test case 'bug464403.js' in gdb:

    python ../trace-test/trace-test.py shell/js bug464403 -d

Any substring of 'bug464403.js' that is not a substring of any other test name will also work.
Attachment #399927 - Flags: review?(dvander)
Attachment #399927 - Flags: review?(dvander) → review+
Pushed to TM as 8028fd050632.
Whiteboard: fixed-in-tracemonkey
Based on past precedent (dist/bin/firefox, run-mozilla.sh, et al.), if I had to guess at the argument to invoke a debugger, it'd be -g, and I believe -d would instead be the argument to specify a specific debugger.  Maybe worth changing to -g for consistency?
(In reply to comment #2)
> Based on past precedent (dist/bin/firefox, run-mozilla.sh, et al.), if I had to
> guess at the argument to invoke a debugger, it'd be -g, and I believe -d would
> instead be the argument to specify a specific debugger.  Maybe worth changing
> to -g for consistency?

Any objections? If no one objects by this afternoon, I'll just change it quick.
Option is now -g. This change pushed to TM as 435dc871ba9d.
http://hg.mozilla.org/mozilla-central/rev/8028fd050632
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Flags: in-testsuite-
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: