Not sure how relevant this is to the issue in Xerces-C, but a long time ago I added a feature [1][2] to Xerces-J to make it less likely that a stack overflow would occur while parsing the DTD.
[1] http://xerces.apache.org/xerces2-j/features.html#validation.balance-syntax-trees [2] http://svn.apache.org/viewvc/xerces/java/trunk/src/org/apache/xerces/impl/dtd/BalancedDTDGrammar.java?view=markup&pathrev=965320 Michael Glavassevich XML Technologies and WAS Development IBM Toronto Lab E-mail: mrgla...@ca.ibm.com E-mail: mrgla...@apache.org Alberto Massari <albertomass...@tiscali.it> wrote on 06/04/2016 03:28:40 PM: > Hi Scott, > I can give it a few days to see if a stack-based approach can be done, > like I did for the XMLSchema processing a while ago > > Alberto > > Il 04/06/16 18:17, Cantor, Scott ha scritto: > > This is a shot in the dark, but if there's anybody using Xerces-C > that might have some experience with the DTD implementation in it, > or that has a real need for it to work well, a lot of the recent > bugs coming in are connected to the DTD parsing code. I'm currently > the person with the bandwidth and enough need to be trying to fix a > lot of the issues that are being reported, and I don't use the DTD > code (in fact I'm about to look into adding a compile time option to > turn it all off), so it's not a great fit. > > > > If you fit the bill, and might be able to spare the time to help > deal with it, please get in touch (here or directly). > > > > -- Scott
