Open
Bug 940930
Opened 10 years ago
Updated 1 year ago
--debugger=lldb doesn't work with reftests
Categories
(Testing :: General, defect)
Testing
General
Tracking
(Not tracked)
NEW
People
(Reporter: froydnj, Unassigned)
Details
Attachments
(1 file)
2.11 KB,
patch
|
Details | Diff | Splinter Review |
Saw this wandering through backscroll on IRC this morning: mattwoodrow | And --debugger=lldb for retests doesn't work Matt, could you elaborate?
Comment 2•10 years ago
|
||
This isn't just bug 914925, right?
Comment 3•10 years ago
|
||
https://pastebin.mozilla.org/3652602 OSX 10.9, lldb-300.2.53, latest m-c.
Flags: needinfo?(matt.woodrow)
Comment 4•10 years ago
|
||
(In reply to Ted Mielczarek [:ted.mielczarek] from comment #2) > This isn't just bug 914925, right? Looks like that didn't change anything for reftests, so I think it is. I tried manually patching runreftest.py, and it seems to work. However, using ctrl-c to try break just killed the app, and made my terminal tab stop accepting input.
Comment 5•10 years ago
|
||
Comment 6•10 years ago
|
||
Looks like this is partially because mach is catching the ctrl-c (SIGINT) signal and exiting. Disabling this (using signal.signal(signal.SIGINT, signal.SIG_IGN)) stops mach from quitting, but I still never get an (lldb) prompt. It appears to break execution correctly, I just have no way of providing input.
Updated•1 year ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•