From: <no...@so...> - 2002-05-30 20:30:50
|
Bugs item #533886, was opened at 2002-03-23 04:39 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=112867&aid=533886&group_id=12867 Category: None Group: None >Status: Closed >Resolution: Wont Fix Priority: 5 Submitted By: Bob Matlin (bmatlin) >Assigned to: Finn Bock (bckfnn) Summary: xmlproc.py parse_start_tag() Initial Comment: xmlproc.py parse_start_tag() can try to access the list self.data past its limit. An updated version is attached. ---------------------------------------------------------------------- >Comment By: Finn Bock (bckfnn) Date: 2002-05-30 22:30 Message: 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. ---------------------------------------------------------------------- Comment By: Lars Marius Garshol (larsga) Date: 2002-05-03 17:22 Message: 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. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=112867&aid=533886&group_id=12867 |