RESOLVED DUPLICATE of bug 26386 34500
Web Inspector: support symbolic breakpoints (break on a function by name) 
https://bugs.webkit.org/show_bug.cgi?id=34500
Summary Web Inspector: support symbolic breakpoints (break on a function by name)
Timothy Hatcher
Reported 2010-02-02 13:18:44 PST
It would be nice to break on a function by name. This is tricky since it would require a full patch to the function (like window.console.log, etc). Or just breaking on "log" would be enough?
Attachments
Add attachment proposed patch, testcase, etc.
Patrick Mueller
Comment 1 2010-02-03 08:10:06 PST
One thing I've been thinking about for a while is to allow client-side frameworks, like Dojo, Closure, etc, to provide a list of functions to the debugger. Many of these frameworks are problematic in that the functions are defined anonymously, but there is typically some "structure" to the way functions are defined - in classes, mixins, etc. The registration/definition process for these classes/methods/etc could be augmented to provide relevant information back to the debugger. I guess the way I envision this is that the debugger would end up having a list of library-defined functions that it could present to the user as breakpoint candidates - or other types of activities (log when a function is hit, etc). Functions are also widely used as event processors/call backs, and many of these client-side frameworks have consistent ways that these are done. The presentation (ie, "label") for these functions would be more like "event handler for XXX" where XXX is some event name. I suppose you might want to provide some kind of grouping for the presentation of the list - this could be library defined groupings; the list could be hierarchical, or even perhaps just two levels - a group and a label within the group. Where might we present a list like this? Another drop-down? A side panel?
Pavel Feldman
Comment 2 2010-02-03 08:51:29 PST
> I guess the way I envision this is that the debugger would end up having a list > of library-defined functions that it could present to the user as breakpoint > candidates - or other types of activities (log when a function is hit, etc). Why not to set breakpoints right in the library source code? Or are you saying searching for the definition takes too long? We could either improve search or provide outline for the source file.
Timothy Hatcher
Comment 3 2010-02-03 09:32:50 PST
*** This bug has been marked as a duplicate of bug 26386 ***
Timothy Hatcher
Comment 4 2010-02-03 09:35:52 PST
Showing a butter name is a whole different issue. We have a bug about generating better names vs (anonomyous function). The JS library could also set the displayName property on the function to show whever they see fit.
Timothy Hatcher
Comment 5 2010-02-03 09:43:45 PST
s/butter/better/. mmmm butter!
Note You need to log in before you can comment on or make changes to this bug.