rzel / monsterdebugger

Automatically exported from code.google.com/p/monsterdebugger
0 stars 0 forks source link

error catching code causing errors #7

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. normal installation and use of MonsterDebugger class
2. tracing an object that results in parseObject error
3. flash debugger spits out 1085 error, swf halts

What is the expected output? 
successful trace to MonsterDebugger

What do you see instead?
error message in flash debugger popup starting with:
TypeError: Error #1085: The element type "node" must be terminated by the
matching end-tag "</node>".

What version of the product are you using? 
2.5.1 stable

On what operating system?
Linux Ubuntu 9.10 Karmic Koala

Please provide any additional information below.

The parsing error triggers a catch that spits out a node like this:
xml += createNode("node", {icon:ICON_WARNING, type:TYPE_WARNING,
label:"Unreadable", name:"Unreadable"}, true);

This node is not closed, resulting int he 1085 xml error. It should be
immediately followed by:

xml += createNode("/node");

In scanning the file, I see this problem occurring in four locations, lines
1033, 1125, 1391 (in parseObject), and 1536 (in parseDisplayObject).

Original issue reported on code.google.com by birnamde...@gmail.com on 10 Feb 2010 at 6:26

GoogleCodeExporter commented 9 years ago
A quick update, as I look further into this.

The information above is a false solution -- that is, it generated valid XML and
stopped the 1085 problem, but it wasn't the correct way to solve the problem.

Looking further, it is the ICON_ROOT node on line 1224 that is not being 
closed, not
the error nodes (which are successfully closed by passing 'true' to the 'close'
parameter).

The actual problem turned out to be on line 1341, which catches only 
error:TypeError.
A different type of error is occurring in my case, which is not handled by this
try/catch. The function quits and the unclosed ICON_ROOT node remains unclosed.
Adding catch(error:Error) to this try/catch block solves the problem. 
(successfully
this time, it appears!)

Sorry for all of the bad information above.

Original comment by birnamde...@gmail.com on 10 Feb 2010 at 7:53

Attachments:

GoogleCodeExporter commented 9 years ago
Also note, this might help with Issue 5 as well.

Original comment by birnamde...@gmail.com on 10 Feb 2010 at 7:53

GoogleCodeExporter commented 9 years ago
New version!

Original comment by ferdikoomenmobile@gmail.com on 5 Apr 2011 at 1:01