Interesting.
I have the latest VS release but I haven’t installed it yet; probably should
have. I wonder how well it will perform. Thanks for the info.
-Andrew Martinez
-----Original
Message-----
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]On Behalf Of Ryan Gahl
Sent: Tuesday, June 06, 2006 9:41
AM
To:
[email protected]
Subject: Re: [Rails-spinoffs]
Monitor Objects
By far the best way to debug IE, Andrew,
is to use VS, or the newly released Visual Web Developer Express which is free.
It's extremely fast for debugging js, and feature rich. Break points, watches,
stack trace, script explorer, etc...
On 6/6/06, Martinez, Andrew
<[EMAIL PROTECTED]>
wrote:
FireFox has an extension called LeakMonitor. It is quite annoying
for normal browsing but you can just enable/disable it.
Have you considered making an absolutely positioned DIV with overflow auto that
can be shown/hidden with key commands for debug output? Just pipe your debug to
a function and then you can just disable the output when you don't need it by
editing the output function. Sprinkle debug statements throughout your code.
OR
You could take the modern approach and use FireFox and the Venkman extension
with is a full debugger. Add the "debugger;" flag at the start of
your script and step through. However, to use Venkman you will have to read the
online manual/tutorial because it requires some non-intuitive setup (at least
from the stand point of standard debuggers).
FireFox has a ton of web developer addons (besides just the plain old web
developer). I suggest FireBug (lets you quickly see error output, css, events,
and HTTP requests/responses for Ajax), console2, and Venkman for a good start.
For IE you have their beta web developer bar and the script debugger. The IE
debugger is pretty useless and poorly implemented. I *think* it responds the
"debugger;" command. In my honest opinion, I don't use IE to develop.
It is strictly a testing browser to make sure my code works properly in IE.
-Andrew Martinez
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:
[EMAIL PROTECTED]] On Behalf Of
Maninder, Singh
Sent: Tuesday, June 06, 2006 9:01 AM
To: [email protected]
Subject: [Rails-spinoffs]
Monitor Objects
Hi,
Sometimes (and I don't know when) I get a Stack Overflow at line 0 error.
I know that it could be due to -
1) Recursion
2) Lot of memory consumption by some object
3) Bad usage of iframes (I read it somewhere:)
4) Something else
Since it's not reproducible everytime, it's hard to debug.
So, I was wondering if using prototype, there is a way to build something like
an object monitor to
keep track of what all objects are currently there in memory and what have been
destroyed?
Thoughts?
Thank you,
Mandy.
p.s. This is primarily for Internet Explorer.
_______________________________________________
Rails-spinoffs mailing list
[email protected]
http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs
_______________________________________________
Rails-spinoffs mailing list
[email protected]
http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs
