Summary: | "out of memory" errors on empty match element in fonts.conf | ||
---|---|---|---|
Product: | fontconfig | Reporter: | Vincent Lefevre <vincent-fdt> |
Component: | library | Assignee: | fontconfig-bugs |
Status: | RESOLVED FIXED | QA Contact: | Behdad Esfahbod <freedesktop> |
Severity: | normal | ||
Priority: | medium | CC: | akira |
Version: | unspecified | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Vincent Lefevre
2013-10-31 11:06:17 UTC
Note: This error can also occur with other conf files, but this time invalid. See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=726985 for instance. You may want to fix both problems at the same time (for an invalid file, an error is OK, but not "out of memory"). (In reply to comment #0) > Under Debian/unstable, after upgrading fontconfig from 2.10.2 to 2.11, I get > "out of memory" errors with the following fonts.conf file: > > <?xml version="1.0"?> > <!DOCTYPE fontconfig SYSTEM "fonts.dtd"> > <fontconfig> > <match target="font"> > <!-- Commented out code. --> > </match> > </fontconfig> > > According to the DTD, it is valid. that is invalid case. DTD says: <!ELEMENT match (test*, edit*)+> match element has to contain one test or edit at least. (In reply to comment #2) > that is invalid case. DTD says: > > <!ELEMENT match (test*, edit*)+> > > match element has to contain one test or edit at least. I don't think so, because you have * after "test" and after "edit". At least, "xmllint --noout --loaddtd --valid" validates the XML file. This is different from: <!ELEMENT match (test | edit)+> (In reply to comment #3) > (In reply to comment #2) > > that is invalid case. DTD says: > > > > <!ELEMENT match (test*, edit*)+> > > > > match element has to contain one test or edit at least. > > I don't think so, because you have * after "test" and after "edit". At > least, "xmllint --noout --loaddtd --valid" validates the XML file. This is > different from: > > <!ELEMENT match (test | edit)+> I misunderstood that then. let me correct for that too. Fixed in git. thanks! |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.