how to actually locate bug in IE

[Andrew Poulos]

I've got a page, that's in a frame in a frameset, that calls multiple
external js files. When I get a message that tells me that a problem
occurred at line, say, 185 is there some way to track down the actual
line of code referred to? At the moment I have no idea where exactly IE
had the problem.

Something like MZ's js console would be nice.

Andrew Poulos

[Hywel Jenkins]

In article <41ba9acd$0$25786$5a62ac22@per-qv1-newsreader-
01.iinet.net.au>, ap*****@hotmail.com says...

I've got a page, that's in a frame in a frameset, that calls multiple
external js files. When I get a message that tells me that a problem
occurred at line, say, 185 is there some way to track down the actual
line of code referred to? At the moment I have no idea where exactly IE
had the problem.

Open each source file in turn and check line 185. Put an alert before
and after, and see which order the pop-ups appear.

--
Hywel http://kibo.org.uk/
I do not eat quiche.

[Duncan Booth]

Andrew Poulos wrote:

I've got a page, that's in a frame in a frameset, that calls multiple
external js files. When I get a message that tells me that a problem
occurred at line, say, 185 is there some way to track down the actual
line of code referred to? At the moment I have no idea where exactly IE
had the problem.

Something like MZ's js console would be nice.

Install Microsoft's script debugger (downloadable from Microsoft's
website) and IE will give you the option of debugging when it hits an
error. The debugger will then open at the correct source line and you can
inspect variables etc. before continuing.

The script debugger isn't very good (it has a tendency to lock up both IE
and itself), but at least it shows you where the error really is.

[Andrew Poulos]

Hywel Jenkins wrote:

In article <41ba9acd$0$25786$5a62ac22@per-qv1-newsreader-
01.iinet.net.au>, ap*****@hotmail.com says...

I've got a page, that's in a frame in a frameset, that calls multiple
external js files. When I get a message that tells me that a problem
occurred at line, say, 185 is there some way to track down the actual
line of code referred to? At the moment I have no idea where exactly IE
had the problem.

Open each source file in turn and check line 185. Put an alert before
and after, and see which order the pop-ups appear.

I'm testing in IE 5 on Win 98SE and the MS script debugger opens at the
top of the first external script file it loaded regardless of where the
error is (stupid software!)

I'm going to have to go through each script file as you suggest. Thanks
for the help.

Andrew Poulos

[Randy Webb]

Andrew Poulos wrote:

Hywel Jenkins wrote:

In article <41ba9acd$0$25786$5a62ac22@per-qv1-newsreader-
01.iinet.net.au>, ap*****@hotmail.com says...

I've got a page, that's in a frame in a frameset, that calls multiple
external js files. When I get a message that tells me that a problem
occurred at line, say, 185 is there some way to track down the actual
line of code referred to? At the moment I have no idea where exactly
IE had the problem.

Open each source file in turn and check line 185. Put an alert before
and after, and see which order the pop-ups appear.

I'm testing in IE 5 on Win 98SE and the MS script debugger opens at the
top of the first external script file it loaded regardless of where the
error is (stupid software!)

I'm going to have to go through each script file as you suggest. Thanks
for the help.

Take all of your external files, put them internal.
Debug.
Remove them back to external files.

It makes tracking line numbers a lot simpler.

--
Randy
comp.lang.javascript FAQ - http://jibbering.com/faq