#6 debugging bombs out mid-way through

[Alan Ezust]

Got no informative messages from inside jedit, but in
the standard error, I got this:

[error] JEditTextArea: BUG:
screenLine=-1,visibleLines=9,physicalLine=38,firstPhysicalLine=28,lastPhysicalLine=36
[error] Thread-5: [Fatal Error] :1:156: The entity name
must immediately follow the '&' in the entity reference.
[error] Thread-5:
org.jymc.jpydebug.PythonDebugException:
JPyDebugXmlParser parse SAX PARSING ERROR : The entity
name must immediately follow the '&' in the entity
reference.
[error] Thread-5: at
org.jymc.jpydebug.JPyDebugXmlParser.parse(JPyDebugXmlParser.java:415)
[error] Thread-5: at
org.jymc.jpydebug.PythonDebugEvent.parse(PythonDebugEvent.java:117)
[error] Thread-5: at
org.jymc.jpydebug.PythonDebugEvent.<init>(PythonDebugEvent.java:167)
[error] Thread-5: at
org.jymc.jpydebug.PythonDebugClient.populateEvent(PythonDebugClient.java:170)
[error] Thread-5: at
org.jymc.jpydebug.PythonDebugClient.access$300(PythonDebugClient.java:34)
[error] Thread-5: at
org.jymc.jpydebug.PythonDebugClient$_TCP_TASK_.run(PythonDebugClient.java:146)
[error] Thread-5: [Fatal Error] :1:1605: The entity
name must immediately follow the '&' in the entity
reference.
[error] Thread-5:
org.jymc.jpydebug.PythonDebugException:
JPyDebugXmlParser parse SAX PARSING ERROR : The entity
name must immediately follow the '&' in the entity
reference.
[error] Thread-5: at
org.jymc.jpydebug.JPyDebugXmlParser.parse(JPyDebugXmlParser.java:415)
[error] Thread-5: at
org.jymc.jpydebug.PythonDebugEvent.parse(PythonDebugEvent.java:117)
[error] Thread-5: at
org.jymc.jpydebug.PythonDebugEvent.<init>(PythonDebugEvent.java:167)
[error] Thread-5: at
org.jymc.jpydebug.PythonDebugClient.populateEvent(PythonDebugClient.java:170)
[error] Thread-5: at
org.jymc.jpydebug.PythonDebugClient.access$300(PythonDebugClient.java:34)
[error] Thread-5: at
org.jymc.jpydebug.PythonDebugClient$_TCP_TASK_.run(PythonDebugClient.java:146)
[error] Thread-5: [Fatal Error] :1:1604: The entity
name must immediately follow the '&' in the entity
reference.
[error] Thread-5:
org.jymc.jpydebug.PythonDebugException:
JPyDebugXmlParser parse SAX PARSING ERROR : The entity
name must immediately follow the '&' in the entity
reference.
[error] Thread-5: at
org.jymc.jpydebug.JPyDebugXmlParser.parse(JPyDebugXmlParser.java:415)
[error] Thread-5: at
org.jymc.jpydebug.PythonDebugEvent.parse(PythonDebugEvent.java:117)
[error] Thread-5: at
org.jymc.jpydebug.PythonDebugEvent.<init>(PythonDebugEvent.java:167)
[error] Thread-5: at
org.jymc.jpydebug.PythonDebugClient.populateEvent(PythonDebugClient.java:170)
[error] Thread-5: at
org.jymc.jpydebug.PythonDebugClient.access$300(PythonDebugClient.java:34)
[error] Thread-5: at
org.jymc.jpydebug.PythonDebugClient$_TCP_TASK_.run(PythonDebugClient.java:146)
[error] JEditTextArea: BUG:
screenLine=-1,visibleLines=9,physicalLine=40,firstPhysicalLine=28,lastPhysicalLine=36

[Jean-Yves MENGANT]

Logged In: YES
user_id=513881

The XML parsers is bombing on client side due to the XML
production of the server backend.
In order to be able to debug this I have added more details
(mainly the XML source production which is at the origin of
the troubles) to be able to fix that.

when the version 0.0.7 will be dropped it will contain the
capalbility of debugging this kind of problems.

[Alan Ezust]

Logged In: YES
user_id=935841

I am not exactly sure what it is about this testcase that is
causing the problem - I've tried removing various pieces to
see what the culprit.
The problem goes away if I remove the classdefinition in the
middle.
The problem also goes away if I remove the try/catch just
before the
before = open(filename).read() line (which is the line which
should throw
an exception - a file not found error).

I am trying the June 21 version now.

[Alan Ezust]

A test case that causes the debugger to bomb

[Alan Ezust]

Logged In: YES
user_id=935841

Have you seen the test case yet?

[Jean-Yves MENGANT]

Logged In: YES
user_id=513881

this should be fixed now (Xml production error in
jpydbg.py)