Issue533886

classification
Title: xmlproc.py parse_start_tag()
Type: Severity: normal
Components: None Versions:
Milestone:
process
Status: closed Resolution: wont fix
Dependencies: Superseder:
Assigned To: bckfnn Nosy List: bckfnn, bmatlin, larsga
Priority: normal Keywords:

Created on 2002-03-23.03:39:32 by bmatlin, last changed 2002-05-30.20:30:49 by bckfnn.

Files
File name Uploaded Description Edit Remove
xmlproc.py bmatlin, 2002-03-23.03:39:32 fixes list limit violation
Messages
msg638 (view) Author: Bob Matlin (bmatlin) Date: 2002-03-23.03:39:32
xmlproc.py parse_start_tag() can try to access the 
list self.data past its limit. An updated version is 
attached.
msg639 (view) Author: Lars Marius Garshol (larsga) Date: 2002-05-03.15:22:10
Logged In: YES 
user_id=39120

That is by design, actually. parse_start_tag, do_parse, 
and parse_end_tag, possibly also the method that parses 
character data all do this. There is code in do_parse to 
catch the generated exceptions and deal with it, since 
accesses outside the buffer will mean that xmlproc is done 
with its current buffer and must wait for more data.

Have you actually run into any problems because of this? 
If so, please report them with sample data that cause them 
to be triggered, but please don't modify the source unless 
you *know* there is a bug.
msg640 (view) Author: Finn Bock (bckfnn) Date: 2002-05-30.20:30:49
Logged In: YES 
user_id=4201

Thank you Lars for responding. I don't fully understand the
bugreport or your explanation, but I' trust that you know
your stuff so I'll close the report.
History
Date User Action Args
2002-03-23 03:39:32bmatlincreate