Last Comment Bug 875034 - (dbg-blackbox) [meta] Debugger blackboxing
(dbg-blackbox)
: [meta] Debugger blackboxing
Status: NEW
:
Product: Firefox
Classification: Client Software
Component: Developer Tools: Debugger (show other bugs)
: unspecified
: x86 Mac OS X
: P5 normal (vote)
: ---
Assigned To: Nobody; OK to take it and work on it
:
: James Long (:jlongster)
Mentors:
Depends on: 905263 905450 905859 905863 905978 923802 952648 1092863 1118152 1208131 877682 877686 892599 892605 895270 895272 895543 895565 898059 898063 899877 901030 901142 901169 901712 901733 903217 905046 905136 924238 933744 967156 1032379 1108042 1111012
Blocks: 917072
  Show dependency treegraph
 
Reported: 2013-05-22 12:31 PDT by Rob Campbell [:rc] (:robcee)
Modified: 2016-03-16 13:23 PDT (History)
11 users (show)
See Also:
Crash Signature:
(edit)
QA Whiteboard:
Iteration: ---
Points: ---
Has Regression Range: ---
Has STR: ---


Attachments

User Story
you want to debug your own code that calls into a library at various points and don't want to step through that alien code. The bug is in your stuff (you hope).      
Description Rob Campbell [:rc] (:robcee) 2013-05-22 12:31:11 PDT
When debugging, it can be useful to "Step Around" library code. I.e., treat libraries as "Black Boxes" for the purposes of debugging.

Use case:
you want to debug your own code that calls into a library at various points and don't want to step through that alien code. The bug is in your stuff (you hope).

Possible Implementation:
It should be possible to implement this in the Debug Server by providing scripts that are known to be libraries. 

(UI could be a context menu on the sources to indicate that this is a library script)

When running in Debug mode, when entering a frame, the Debug Server can check to see if this script url is one of the libraries and continue stepping until the current frame is in a different source url.
Comment 1 Girish Sharma [:Optimizer] 2013-05-22 12:33:26 PDT
plus one that.
I have been recently playing with jQuery a lot and debugging custom functions built around jQuery is a hell. Up to 10 stack frames on line 2 of jquery.min.js and then you finally press the step over button and miss the frame which you were actually looking into.
Comment 2 Sebastian Zartner [:sebo] 2014-11-21 01:24:22 PST
Is this bug restricted to blackboxing within the Debugger panel? If not, bug 1102797 should be blocking it.

Sebastian
Comment 3 Sebastian Zartner [:sebo] 2014-11-21 01:25:23 PST
Sorry, wrong bug. The correct one is bug 905978.

Sebastian
Comment 4 Eddy Bruel [:ejpbruel] 2014-11-21 02:02:50 PST
(In reply to Sebastian Zartner from comment #3)
> Sorry, wrong bug. The correct one is bug 905978.
> 
> Sebastian

Yeah, this bug is restricted to blackboxing within the Debugger panel. But thank you very much for bringing that bug to my attention!
Comment 5 Nick Fitzgerald [:fitzgen] [⏰PDT; UTC-7] 2014-11-21 09:08:18 PST
I mean, it seems like it makes sense to add that bug as a blocker just to keep it tracked, unless we want to add another meta meta blackboxing bug and start getting super bureaucratic and all that...

Eddy?
Comment 6 Eddy Bruel [:ejpbruel] 2014-11-21 10:16:47 PST
(In reply to Nick Fitzgerald [:fitzgen] from comment #5)
> I mean, it seems like it makes sense to add that bug as a blocker just to
> keep it tracked, unless we want to add another meta meta blackboxing bug and
> start getting super bureaucratic and all that...
> 
> Eddy?

I agree that we shouldn't be overly bureaucratic about these things, but I'm a bit worried that I'll lose overview of what bugs belong to the debugger if we also start tracking non-debugger stuff under these meta bugs.

On the other hand, blackboxing is a feature that primarily belongs to the debugger. The fact that we sometimes need to make changes in closely related components doesn't really change that, so I guess it wouldn't hurt to add this bug as a blocker.

If we run into more of these 'related' bugs in the future, let's decide on a case by case basis whether to add them to one of these meta bugs or not. Does that sound reasonable for now?

Note You need to log in before you can comment on or make changes to this bug.