I tried the Firebug 1.4's *Break On Next *feature. It is very close to what I mean.
But it seems that the attempts of reverse engineering most events (e.g. mouse clicks, key presses) are easily deviated by *mouseover *event handlers that are never of my interests. Mouseover event is keeping capturing every "next" breakpoints all the time. Is there a way to circumvent this? Or am I on the right track of experiencing the new feature? Thanks, Canny On Fri, Jun 26, 2009 at 4:59 PM, johnjbarton <[email protected]>wrote: > > In Firebug 1.4, the Break On Next button will break in to Javascript > on the next event. It is the double bar thing. > In Firebug 1.5, we plan to have BreakOn features for all of the > panels, so you will be able to break on > next javascript (Script) > request (Net) > response (Net) > DOM mutate mozPaint (HTML) > Style change (CSS if we can figure it out). > Error (Console) > jjb > > On Jun 26, 1:37 pm, Yan Huang <[email protected]> wrote: > > But I am using firebug on someone else's web service only available > online. > > Strictly speaking, I am > > not debugging the application, rather trying to reverse engineering part > of > > the application. > > > > I guess most sophisticated debugging tools like *gdb* offer this feature > > (i.e., break on arbitrary function > > invocation point specified by a string name). I am not sure whether there > is > > a traditional debugger that > > can break at event-handling functions for an arbitrary event specified by > > its string name. I think this is > > indeed a very useful feature for working with JavaScript programs too. > > > > If Firebug can't do this for the moment, anyone knows other tools offer > the > > functionality for JavaScript? > > > > --- Canny > > > > On Fri, Jun 26, 2009 at 3:54 PM, Kara Rawson <[email protected]> > wrote: > > > > > Canny wrote: > > > > What I am looking for is actually a little bit different from an > > > > ordinary conditional break. What I want to do > > > > is to automatically pause at certain event handlers, e.g., a key > press > > > > event, without explicitly identifying the > > > > location of the event handlers function. This is interesting in cases > > > > where the whole JS file is obfuscated so that > > > > it is hard to find the handler's entry point. Another use case > > > > motivating this debugging feature is that sometimes > > > > you may want the program to pause whenever the XMLHttpRequest send() > > > > is invoked, while it might be tedious > > > > to exhaust every appearance of the send() function call. > > > > > > --- Canny > > > > > > On Jun 26, 2:44 pm, Kara Rawson <[email protected]> wrote: > > > > > >> Canny wrote: > > > > > >>> Hi guys, > > > > > >>> I am fresh to this charming web application debugging tool. But > after > > > >>> some study, I still can't find a way to setup breakpoints in JS > file > > > >>> so that every time certain event is triggered, the execution will > > > >>> pause there in debugging mode. Is this really possible with > Firebug? > > > > > >>> Thanks, > > > >>> Canny > > > > > >> go to the script tab, select the resource you wanna debugg, then > click > > > >> all the way on the left of the line number of the line you wana > break. > > > >> if you click the breakpoints tab on the panel to the right of this > you > > > >> will see an itemized list of break points, you can also click on > watch > > > >> tab to set watches on specifc classes, functions or class members > > > >> (variables). > > > > > >> kara > > > > > if you wanna break at an event, create a new function which listens > > > and/or intercepts these events. the function doesn't have to really do > > > anything, then in your debugger just put a break at where you declare > > > your function. the debugger will pause the app everytime this function > > > gets called, IE when the event is triggered. > > > > > debuggers do not let your break on conditions like that, thats is not > > > what they are designed for or how they work, atleast in the java and js > > > worlds. > > > > > kara > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Firebug" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/firebug?hl=en -~----------~----~----~----~------~----~------~--~---
