Open Bug 1000317 Opened 10 years ago Updated 2 years ago

UI for attempts to use variables that are optimized away

Categories

(DevTools :: Debugger, enhancement, P5)

x86
macOS
enhancement

Tracking

(Not tracked)

People

(Reporter: fitzgen, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [polish-backlog])

As I mention in https://bugzilla.mozilla.org/show_bug.cgi?id=941287#c5, it would be nice if we had some UI to tell the user that the binding they are attempting to access has been optimized away and they can't rely on the result (or we shouldn't even give them a result).

I'm imagining either a new Debugger API completion value that represents the undefined result of a computation that relies on optimized away variables or a known error type that would be thrown (|Debugger.OptimizedAwayBindingError| or something) that we could check for.

Both cases would rely on some jsdbg2 support but it's not clear to me yet exactly how much or what.
Err -- that was supposed to be a link to bug 941287 comment 6 (not 5).
Summary: UI for evals via console, watch expression or conditional breakpoint that attempt to use optimized away variables → UI for attempts to use variables that are optimized away
Whiteboard: [polish-backlog]
Priority: -- → P3
Product: Firefox → DevTools
Priority: P3 → P5
Type: defect → enhancement
Blocks: 1565711
Blocks: 1565713
No longer blocks: 1565711
No longer blocks: 1565713
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.