Hello, again: To be more specific im intrested in what part of the code builds the list in the watch tab (variables and objects like navigator, etc) when the debbuger stop at a certain breakpoint. Thanks. Lautaro
On Mon, Aug 23, 2010 at 12:53 PM, Lautaro Dolberg <[email protected] > wrote: > > > On Fri, Aug 13, 2010 at 7:02 PM, John J Barton < > [email protected]> wrote: > >> >> >> On Aug 13, 9:49 am, lingg <[email protected]> wrote: >> > Hi folks, >> > >> > as it is my first post to this group, I want to acknowledge all the >> > contributors that made firebug possible. I is fare the best tool for >> > web development and makes my life much easier, thanks! >> >> Thanks for the encouragement! >> >> > >> > I like a lot the feature, that makes the debugger break on every >> > error. That really saves time! But there is one aspect you could >> > improve: it is normal practice to user try-catch statements that >> > except errors. Using both, the try statements and autobreak is not >> > usefull as you are supposed to continue a lot of breaks. >> > >> > Is it possible to introduce a configuration to disable the autobreak >> > at errors within try statements? >> >> Yes, but this feature requires help from the internals of Firefox. >> When an error occurs the callstack points to the error. To know if >> there is a catch block we have to look at the enclosing blocks in >> every function on the stack. But we have no access to the enclosing >> blocks other than the names of variables declared. > > We've asked for >> this information, but we've asked for a lot of other things as well >> but nothing come of asking. I guess we just have to wait for someone >> in Mozillla to want such a feature. >> >> What you can do as an alternative is to use Firebug > Console > mini- >> menu > ShowStackTrace for errors, plus, when an error occurs, set an >> error breakpoint and re-run. In the Console to the left of the error >> you will see a place for setting the error breakpoint. >> >> jjb >> > >> > Cheers, >> > Christoph >> >> -- >> 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]<firebug%[email protected]> >> . >> For more options, visit this group at >> http://groups.google.com/group/firebug?hl=en. >> >> > Hello: > Im intrested in getting access to the variables declared of an enclosing > block, or at certain breakpoint at a given script. > I have asked mozilla ppl how I can do that with JSD, an then I got this > code. > http://code.google.com/p/gpsee/source/browse/extras/gsrdb/gsrdb.js#104<http://code.google.com/p/gpsee/source/browse/extras/gsrdb/gsrdb.js#1042> > 2 > But the way they are using the jsd object does not match the interface I > have been using > http://mxr.mozilla.org/mozilla1.9.2/source/js/jsd/idl/jsdIDebuggerService.idl > Im wondering if anybody can point me or tell me where I should take a look > to figure out how firebug get this access? > Thanks in advance. > Lautaro > -- 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.
