From noreply at sourceforge.net Mon Feb 2 01:15:32 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Feb 2 01:15:36 2004 Subject: [Expat-bugs] [ expat-Patches-888879 ] gb2312 encoding handle Message-ID: Patches item #888879, was opened at 2004-02-02 14:15 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=310127&aid=888879&group_id=10127 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: hunter,liu (szhunter) Assigned to: Nobody/Anonymous (nobody) Summary: gb2312 encoding handle Initial Comment: an patch for expat that can let expat handle gb2312 encoding xml file. Developer must use Xml_SetUnknowEncodingHandle() to call XML_GbEncodingHandle() ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=310127&aid=888879&group_id=10127 From noreply at sourceforge.net Thu Feb 5 14:28:01 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Feb 5 14:28:09 2004 Subject: [Expat-bugs] [ expat-Bugs-891265 ] Support for XML 1.1 Message-ID: Bugs item #891265, was opened at 2004-02-05 19:28 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=891265&group_id=10127 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Xanthor (eldarendil) Assigned to: Nobody/Anonymous (nobody) Summary: Support for XML 1.1 Initial Comment: Hello I'd like to know if you plan to support XML 1.1, and when ? ;?) (The roadmap isn't really clear about that..) Thanks. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=891265&group_id=10127 From noreply at sourceforge.net Sat Feb 7 09:15:24 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Feb 7 09:15:36 2004 Subject: [Expat-bugs] [ expat-Bugs-891265 ] Support for XML 1.1 Message-ID: Bugs item #891265, was opened at 2004-02-05 14:28 Message generated for change (Comment added) made by kwaclaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=891265&group_id=10127 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Xanthor (eldarendil) Assigned to: Nobody/Anonymous (nobody) Summary: Support for XML 1.1 Initial Comment: Hello I'd like to know if you plan to support XML 1.1, and when ? ;?) (The roadmap isn't really clear about that..) Thanks. ---------------------------------------------------------------------- >Comment By: Karl Waclawek (kwaclaw) Date: 2004-02-07 09:15 Message: Logged In: YES user_id=290026 Yes, we have the intention to support XML 1.1, now that it is an official recommendation. However, we do not have a time line yet. It really depends on who will donate his/her time and effort. Karl ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=891265&group_id=10127 From noreply at sourceforge.net Sat Feb 7 09:19:06 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Feb 7 09:19:17 2004 Subject: [Expat-bugs] [ expat-Patches-888879 ] gb2312 encoding handle Message-ID: Patches item #888879, was opened at 2004-02-02 01:15 Message generated for change (Comment added) made by kwaclaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=310127&aid=888879&group_id=10127 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: hunter,liu (szhunter) Assigned to: Nobody/Anonymous (nobody) Summary: gb2312 encoding handle Initial Comment: an patch for expat that can let expat handle gb2312 encoding xml file. Developer must use Xml_SetUnknowEncodingHandle() to call XML_GbEncodingHandle() ---------------------------------------------------------------------- >Comment By: Karl Waclawek (kwaclaw) Date: 2004-02-07 09:19 Message: Logged In: YES user_id=290026 Thank you for your patch! For now we will leave it as a standalone patch, as we have not yet determined in which way support for additional encodings should be added to Expat. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=310127&aid=888879&group_id=10127 From noreply at sourceforge.net Thu Feb 12 19:11:24 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Feb 12 19:12:06 2004 Subject: [Expat-bugs] [ expat-Bugs-896188 ] Not well-formed internal parameter entities Message-ID: Bugs item #896188, was opened at 2004-02-12 17:11 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=896188&group_id=10127 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Jeremy Kloth (jkloth) Assigned to: Nobody/Anonymous (nobody) Summary: Not well-formed internal parameter entities Initial Comment: In testing against the XML Conformance Test Suites, we've discovered that Expat doesn't verify that internal parameter entities are well-formed (as per XML 1.0 3rd 4.3.2). Attached is a patch that fixes this and 2 example documents that demonstrate both valid and invalid behavior. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=896188&group_id=10127 From noreply at sourceforge.net Thu Feb 12 20:13:46 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Feb 12 20:14:27 2004 Subject: [Expat-bugs] [ expat-Bugs-896188 ] Not well-formed internal parameter entities Message-ID: Bugs item #896188, was opened at 2004-02-12 19:11 Message generated for change (Comment added) made by kwaclaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=896188&group_id=10127 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Jeremy Kloth (jkloth) >Assigned to: Karl Waclawek (kwaclaw) Summary: Not well-formed internal parameter entities Initial Comment: In testing against the XML Conformance Test Suites, we've discovered that Expat doesn't verify that internal parameter entities are well-formed (as per XML 1.0 3rd 4.3.2). Attached is a patch that fixes this and 2 example documents that demonstrate both valid and invalid behavior. ---------------------------------------------------------------------- >Comment By: Karl Waclawek (kwaclaw) Date: 2004-02-12 20:13 Message: Logged In: YES user_id=290026 I tried the current Expat (CVS), and it reports a syntax error on line 5, column 0 for bad.xml. Is that not what it should do? Are you saying that your copy of Expat doesn't do that? Which version are you using? Which test cases of the XML conformance suite does Expat not pass - related to this issue? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=896188&group_id=10127 From noreply at sourceforge.net Thu Feb 12 20:52:17 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Feb 12 20:53:02 2004 Subject: [Expat-bugs] [ expat-Bugs-896188 ] Not well-formed internal parameter entities Message-ID: Bugs item #896188, was opened at 2004-02-12 17:11 Message generated for change (Comment added) made by jkloth You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=896188&group_id=10127 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Jeremy Kloth (jkloth) Assigned to: Karl Waclawek (kwaclaw) Summary: Not well-formed internal parameter entities Initial Comment: In testing against the XML Conformance Test Suites, we've discovered that Expat doesn't verify that internal parameter entities are well-formed (as per XML 1.0 3rd 4.3.2). Attached is a patch that fixes this and 2 example documents that demonstrate both valid and invalid behavior. ---------------------------------------------------------------------- >Comment By: Jeremy Kloth (jkloth) Date: 2004-02-12 18:52 Message: Logged In: YES user_id=38980 Actually, the error should be on line 4 (the %e; expansion). I'm using a CVS (updated today) build. I've attached another invalid example to further demonstrate the problem. The XML Test Suite tests for this case are xmltest/not-wf/not-sa/010.xml and 011.xml ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2004-02-12 18:13 Message: Logged In: YES user_id=290026 I tried the current Expat (CVS), and it reports a syntax error on line 5, column 0 for bad.xml. Is that not what it should do? Are you saying that your copy of Expat doesn't do that? Which version are you using? Which test cases of the XML conformance suite does Expat not pass - related to this issue? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=896188&group_id=10127 From noreply at sourceforge.net Thu Feb 12 21:02:40 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Feb 12 21:03:22 2004 Subject: [Expat-bugs] [ expat-Bugs-896188 ] Not well-formed internal parameter entities Message-ID: Bugs item #896188, was opened at 2004-02-12 19:11 Message generated for change (Comment added) made by kwaclaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=896188&group_id=10127 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Jeremy Kloth (jkloth) Assigned to: Karl Waclawek (kwaclaw) Summary: Not well-formed internal parameter entities Initial Comment: In testing against the XML Conformance Test Suites, we've discovered that Expat doesn't verify that internal parameter entities are well-formed (as per XML 1.0 3rd 4.3.2). Attached is a patch that fixes this and 2 example documents that demonstrate both valid and invalid behavior. ---------------------------------------------------------------------- >Comment By: Karl Waclawek (kwaclaw) Date: 2004-02-12 21:02 Message: Logged In: YES user_id=290026 OK, now I remember. If you look at bug #569461 there was a discussion regarding these two test cases, (a while back) and there I thought it would require some time to understand the logic in Expat well enough for a fix. This is cool - having a fix for that! Thanks! I would like you to explain the logic behind the fix, because I really don't want to "fix" Expat so short before a new release unless I understand the fix and can reasonably be sure it doesn't mess up anything else. You might want to create a "Fix Explained" attachment rather than a note, as this web interface really isn't a good text editor. ---------------------------------------------------------------------- Comment By: Jeremy Kloth (jkloth) Date: 2004-02-12 20:52 Message: Logged In: YES user_id=38980 Actually, the error should be on line 4 (the %e; expansion). I'm using a CVS (updated today) build. I've attached another invalid example to further demonstrate the problem. The XML Test Suite tests for this case are xmltest/not-wf/not-sa/010.xml and 011.xml ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2004-02-12 20:13 Message: Logged In: YES user_id=290026 I tried the current Expat (CVS), and it reports a syntax error on line 5, column 0 for bad.xml. Is that not what it should do? Are you saying that your copy of Expat doesn't do that? Which version are you using? Which test cases of the XML conformance suite does Expat not pass - related to this issue? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=896188&group_id=10127 From noreply at sourceforge.net Thu Feb 12 21:28:37 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Feb 12 21:30:14 2004 Subject: [Expat-bugs] [ expat-Bugs-896188 ] Not well-formed internal parameter entities Message-ID: Bugs item #896188, was opened at 2004-02-12 17:11 Message generated for change (Comment added) made by jkloth You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=896188&group_id=10127 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Jeremy Kloth (jkloth) Assigned to: Karl Waclawek (kwaclaw) Summary: Not well-formed internal parameter entities Initial Comment: In testing against the XML Conformance Test Suites, we've discovered that Expat doesn't verify that internal parameter entities are well-formed (as per XML 1.0 3rd 4.3.2). Attached is a patch that fixes this and 2 example documents that demonstrate both valid and invalid behavior. ---------------------------------------------------------------------- >Comment By: Jeremy Kloth (jkloth) Date: 2004-02-12 19:28 Message: Logged In: YES user_id=38980 Attached is the "Fix Explained" (hopefully) document. ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2004-02-12 19:02 Message: Logged In: YES user_id=290026 OK, now I remember. If you look at bug #569461 there was a discussion regarding these two test cases, (a while back) and there I thought it would require some time to understand the logic in Expat well enough for a fix. This is cool - having a fix for that! Thanks! I would like you to explain the logic behind the fix, because I really don't want to "fix" Expat so short before a new release unless I understand the fix and can reasonably be sure it doesn't mess up anything else. You might want to create a "Fix Explained" attachment rather than a note, as this web interface really isn't a good text editor. ---------------------------------------------------------------------- Comment By: Jeremy Kloth (jkloth) Date: 2004-02-12 18:52 Message: Logged In: YES user_id=38980 Actually, the error should be on line 4 (the %e; expansion). I'm using a CVS (updated today) build. I've attached another invalid example to further demonstrate the problem. The XML Test Suite tests for this case are xmltest/not-wf/not-sa/010.xml and 011.xml ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2004-02-12 18:13 Message: Logged In: YES user_id=290026 I tried the current Expat (CVS), and it reports a syntax error on line 5, column 0 for bad.xml. Is that not what it should do? Are you saying that your copy of Expat doesn't do that? Which version are you using? Which test cases of the XML conformance suite does Expat not pass - related to this issue? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=896188&group_id=10127 From noreply at sourceforge.net Thu Feb 12 22:39:16 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Feb 12 22:39:58 2004 Subject: [Expat-bugs] [ expat-Bugs-896188 ] Not well-formed internal parameter entities Message-ID: Bugs item #896188, was opened at 2004-02-12 19:11 Message generated for change (Comment added) made by kwaclaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=896188&group_id=10127 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Jeremy Kloth (jkloth) Assigned to: Karl Waclawek (kwaclaw) Summary: Not well-formed internal parameter entities Initial Comment: In testing against the XML Conformance Test Suites, we've discovered that Expat doesn't verify that internal parameter entities are well-formed (as per XML 1.0 3rd 4.3.2). Attached is a patch that fixes this and 2 example documents that demonstrate both valid and invalid behavior. ---------------------------------------------------------------------- >Comment By: Karl Waclawek (kwaclaw) Date: 2004-02-12 22:39 Message: Logged In: YES user_id=290026 Well, the patch seems to fix the two test cases mentioned below, but when I ran Expat through the whole test suite again, it turned out that it now fails on 32 test cases more than before. One example: test case xmlconf/sun/valid/optional.xml uses the dtdtest.dtd in the same directory. It is well-formed and valid, but Expat now reports a syntax error on line 19, column 26 of the dtd. Seems this patch should be examined more closely. But I wouldn't give up yet. ---------------------------------------------------------------------- Comment By: Jeremy Kloth (jkloth) Date: 2004-02-12 21:28 Message: Logged In: YES user_id=38980 Attached is the "Fix Explained" (hopefully) document. ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2004-02-12 21:02 Message: Logged In: YES user_id=290026 OK, now I remember. If you look at bug #569461 there was a discussion regarding these two test cases, (a while back) and there I thought it would require some time to understand the logic in Expat well enough for a fix. This is cool - having a fix for that! Thanks! I would like you to explain the logic behind the fix, because I really don't want to "fix" Expat so short before a new release unless I understand the fix and can reasonably be sure it doesn't mess up anything else. You might want to create a "Fix Explained" attachment rather than a note, as this web interface really isn't a good text editor. ---------------------------------------------------------------------- Comment By: Jeremy Kloth (jkloth) Date: 2004-02-12 20:52 Message: Logged In: YES user_id=38980 Actually, the error should be on line 4 (the %e; expansion). I'm using a CVS (updated today) build. I've attached another invalid example to further demonstrate the problem. The XML Test Suite tests for this case are xmltest/not-wf/not-sa/010.xml and 011.xml ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2004-02-12 20:13 Message: Logged In: YES user_id=290026 I tried the current Expat (CVS), and it reports a syntax error on line 5, column 0 for bad.xml. Is that not what it should do? Are you saying that your copy of Expat doesn't do that? Which version are you using? Which test cases of the XML conformance suite does Expat not pass - related to this issue? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=896188&group_id=10127 From noreply at sourceforge.net Fri Feb 13 00:01:40 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Feb 13 00:02:20 2004 Subject: [Expat-bugs] [ expat-Bugs-896188 ] Not well-formed internal parameter entities Message-ID: Bugs item #896188, was opened at 2004-02-12 19:11 Message generated for change (Comment added) made by kwaclaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=896188&group_id=10127 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Jeremy Kloth (jkloth) Assigned to: Karl Waclawek (kwaclaw) Summary: Not well-formed internal parameter entities Initial Comment: In testing against the XML Conformance Test Suites, we've discovered that Expat doesn't verify that internal parameter entities are well-formed (as per XML 1.0 3rd 4.3.2). Attached is a patch that fixes this and 2 example documents that demonstrate both valid and invalid behavior. ---------------------------------------------------------------------- >Comment By: Karl Waclawek (kwaclaw) Date: 2004-02-13 00:01 Message: Logged In: YES user_id=290026 One more comment: It seems that Well-formedness constraint: PE Between Declarations applies here rather than section 4.3.2. I guess the solution might involve modifying the processInternalEntity() function in such a way, that the state before and after calling doProlog() is checked for two things: 1) is this a PE reference between declarations? 2) if yes, how does it return - any incomplete declarations? ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2004-02-12 22:39 Message: Logged In: YES user_id=290026 Well, the patch seems to fix the two test cases mentioned below, but when I ran Expat through the whole test suite again, it turned out that it now fails on 32 test cases more than before. One example: test case xmlconf/sun/valid/optional.xml uses the dtdtest.dtd in the same directory. It is well-formed and valid, but Expat now reports a syntax error on line 19, column 26 of the dtd. Seems this patch should be examined more closely. But I wouldn't give up yet. ---------------------------------------------------------------------- Comment By: Jeremy Kloth (jkloth) Date: 2004-02-12 21:28 Message: Logged In: YES user_id=38980 Attached is the "Fix Explained" (hopefully) document. ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2004-02-12 21:02 Message: Logged In: YES user_id=290026 OK, now I remember. If you look at bug #569461 there was a discussion regarding these two test cases, (a while back) and there I thought it would require some time to understand the logic in Expat well enough for a fix. This is cool - having a fix for that! Thanks! I would like you to explain the logic behind the fix, because I really don't want to "fix" Expat so short before a new release unless I understand the fix and can reasonably be sure it doesn't mess up anything else. You might want to create a "Fix Explained" attachment rather than a note, as this web interface really isn't a good text editor. ---------------------------------------------------------------------- Comment By: Jeremy Kloth (jkloth) Date: 2004-02-12 20:52 Message: Logged In: YES user_id=38980 Actually, the error should be on line 4 (the %e; expansion). I'm using a CVS (updated today) build. I've attached another invalid example to further demonstrate the problem. The XML Test Suite tests for this case are xmltest/not-wf/not-sa/010.xml and 011.xml ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2004-02-12 20:13 Message: Logged In: YES user_id=290026 I tried the current Expat (CVS), and it reports a syntax error on line 5, column 0 for bad.xml. Is that not what it should do? Are you saying that your copy of Expat doesn't do that? Which version are you using? Which test cases of the XML conformance suite does Expat not pass - related to this issue? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=896188&group_id=10127 From noreply at sourceforge.net Fri Feb 13 00:34:08 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Feb 13 00:35:06 2004 Subject: [Expat-bugs] [ expat-Bugs-896188 ] Not well-formed internal parameter entities Message-ID: Bugs item #896188, was opened at 2004-02-12 17:11 Message generated for change (Comment added) made by jkloth You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=896188&group_id=10127 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Jeremy Kloth (jkloth) Assigned to: Karl Waclawek (kwaclaw) Summary: Not well-formed internal parameter entities Initial Comment: In testing against the XML Conformance Test Suites, we've discovered that Expat doesn't verify that internal parameter entities are well-formed (as per XML 1.0 3rd 4.3.2). Attached is a patch that fixes this and 2 example documents that demonstrate both valid and invalid behavior. ---------------------------------------------------------------------- >Comment By: Jeremy Kloth (jkloth) Date: 2004-02-12 22:34 Message: Logged In: YES user_id=38980 OK. After going through the spec again, we came to the same conclusion (WFC: PE Between Declarations). Adding a new patch which uses this for its check as opposed to just checking if it is a parameter entity. ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2004-02-12 22:01 Message: Logged In: YES user_id=290026 One more comment: It seems that Well-formedness constraint: PE Between Declarations applies here rather than section 4.3.2. I guess the solution might involve modifying the processInternalEntity() function in such a way, that the state before and after calling doProlog() is checked for two things: 1) is this a PE reference between declarations? 2) if yes, how does it return - any incomplete declarations? ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2004-02-12 20:39 Message: Logged In: YES user_id=290026 Well, the patch seems to fix the two test cases mentioned below, but when I ran Expat through the whole test suite again, it turned out that it now fails on 32 test cases more than before. One example: test case xmlconf/sun/valid/optional.xml uses the dtdtest.dtd in the same directory. It is well-formed and valid, but Expat now reports a syntax error on line 19, column 26 of the dtd. Seems this patch should be examined more closely. But I wouldn't give up yet. ---------------------------------------------------------------------- Comment By: Jeremy Kloth (jkloth) Date: 2004-02-12 19:28 Message: Logged In: YES user_id=38980 Attached is the "Fix Explained" (hopefully) document. ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2004-02-12 19:02 Message: Logged In: YES user_id=290026 OK, now I remember. If you look at bug #569461 there was a discussion regarding these two test cases, (a while back) and there I thought it would require some time to understand the logic in Expat well enough for a fix. This is cool - having a fix for that! Thanks! I would like you to explain the logic behind the fix, because I really don't want to "fix" Expat so short before a new release unless I understand the fix and can reasonably be sure it doesn't mess up anything else. You might want to create a "Fix Explained" attachment rather than a note, as this web interface really isn't a good text editor. ---------------------------------------------------------------------- Comment By: Jeremy Kloth (jkloth) Date: 2004-02-12 18:52 Message: Logged In: YES user_id=38980 Actually, the error should be on line 4 (the %e; expansion). I'm using a CVS (updated today) build. I've attached another invalid example to further demonstrate the problem. The XML Test Suite tests for this case are xmltest/not-wf/not-sa/010.xml and 011.xml ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2004-02-12 18:13 Message: Logged In: YES user_id=290026 I tried the current Expat (CVS), and it reports a syntax error on line 5, column 0 for bad.xml. Is that not what it should do? Are you saying that your copy of Expat doesn't do that? Which version are you using? Which test cases of the XML conformance suite does Expat not pass - related to this issue? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=896188&group_id=10127 From noreply at sourceforge.net Fri Feb 13 01:14:33 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Feb 13 01:15:17 2004 Subject: [Expat-bugs] [ expat-Bugs-896188 ] Not well-formed internal parameter entities Message-ID: Bugs item #896188, was opened at 2004-02-12 19:11 Message generated for change (Comment added) made by kwaclaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=896188&group_id=10127 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Jeremy Kloth (jkloth) Assigned to: Karl Waclawek (kwaclaw) Summary: Not well-formed internal parameter entities Initial Comment: In testing against the XML Conformance Test Suites, we've discovered that Expat doesn't verify that internal parameter entities are well-formed (as per XML 1.0 3rd 4.3.2). Attached is a patch that fixes this and 2 example documents that demonstrate both valid and invalid behavior. ---------------------------------------------------------------------- >Comment By: Karl Waclawek (kwaclaw) Date: 2004-02-13 01:14 Message: Logged In: YES user_id=290026 This new patch seems to work with the test-suite. Will have a closer look tomorrow. (There was a warning about integral size mismatch). ---------------------------------------------------------------------- Comment By: Jeremy Kloth (jkloth) Date: 2004-02-13 00:34 Message: Logged In: YES user_id=38980 OK. After going through the spec again, we came to the same conclusion (WFC: PE Between Declarations). Adding a new patch which uses this for its check as opposed to just checking if it is a parameter entity. ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2004-02-13 00:01 Message: Logged In: YES user_id=290026 One more comment: It seems that Well-formedness constraint: PE Between Declarations applies here rather than section 4.3.2. I guess the solution might involve modifying the processInternalEntity() function in such a way, that the state before and after calling doProlog() is checked for two things: 1) is this a PE reference between declarations? 2) if yes, how does it return - any incomplete declarations? ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2004-02-12 22:39 Message: Logged In: YES user_id=290026 Well, the patch seems to fix the two test cases mentioned below, but when I ran Expat through the whole test suite again, it turned out that it now fails on 32 test cases more than before. One example: test case xmlconf/sun/valid/optional.xml uses the dtdtest.dtd in the same directory. It is well-formed and valid, but Expat now reports a syntax error on line 19, column 26 of the dtd. Seems this patch should be examined more closely. But I wouldn't give up yet. ---------------------------------------------------------------------- Comment By: Jeremy Kloth (jkloth) Date: 2004-02-12 21:28 Message: Logged In: YES user_id=38980 Attached is the "Fix Explained" (hopefully) document. ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2004-02-12 21:02 Message: Logged In: YES user_id=290026 OK, now I remember. If you look at bug #569461 there was a discussion regarding these two test cases, (a while back) and there I thought it would require some time to understand the logic in Expat well enough for a fix. This is cool - having a fix for that! Thanks! I would like you to explain the logic behind the fix, because I really don't want to "fix" Expat so short before a new release unless I understand the fix and can reasonably be sure it doesn't mess up anything else. You might want to create a "Fix Explained" attachment rather than a note, as this web interface really isn't a good text editor. ---------------------------------------------------------------------- Comment By: Jeremy Kloth (jkloth) Date: 2004-02-12 20:52 Message: Logged In: YES user_id=38980 Actually, the error should be on line 4 (the %e; expansion). I'm using a CVS (updated today) build. I've attached another invalid example to further demonstrate the problem. The XML Test Suite tests for this case are xmltest/not-wf/not-sa/010.xml and 011.xml ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2004-02-12 20:13 Message: Logged In: YES user_id=290026 I tried the current Expat (CVS), and it reports a syntax error on line 5, column 0 for bad.xml. Is that not what it should do? Are you saying that your copy of Expat doesn't do that? Which version are you using? Which test cases of the XML conformance suite does Expat not pass - related to this issue? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=896188&group_id=10127 From noreply at sourceforge.net Fri Feb 13 13:21:19 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Feb 13 13:22:06 2004 Subject: [Expat-bugs] [ expat-Bugs-896188 ] Not well-formed internal parameter entities Message-ID: Bugs item #896188, was opened at 2004-02-12 19:11 Message generated for change (Comment added) made by kwaclaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=896188&group_id=10127 Category: None >Group: Test Required Status: Open >Resolution: Fixed Priority: 5 Submitted By: Jeremy Kloth (jkloth) >Assigned to: Fred L. Drake, Jr. (fdrake) Summary: Not well-formed internal parameter entities Initial Comment: In testing against the XML Conformance Test Suites, we've discovered that Expat doesn't verify that internal parameter entities are well-formed (as per XML 1.0 3rd 4.3.2). Attached is a patch that fixes this and 2 example documents that demonstrate both valid and invalid behavior. ---------------------------------------------------------------------- >Comment By: Karl Waclawek (kwaclaw) Date: 2004-02-13 13:21 Message: Logged In: YES user_id=290026 I applied a simplified version of Jeremy's second patch. Tested with the OASIS test-suite as well as with a read buffer size of 1, to stress test the buffer boundary handling, since we changed some code involving XML_TOK_NONE. This means that we now pass the two test cases of the test suite, xmltest/not-wf/not-sa/010.xml and xmltest/not-wf/not-sa/011.xml, that we previously failed. Check xmlparse.c rev. 1.123 and xmlrole.c rev. 1.16. ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2004-02-13 01:14 Message: Logged In: YES user_id=290026 This new patch seems to work with the test-suite. Will have a closer look tomorrow. (There was a warning about integral size mismatch). ---------------------------------------------------------------------- Comment By: Jeremy Kloth (jkloth) Date: 2004-02-13 00:34 Message: Logged In: YES user_id=38980 OK. After going through the spec again, we came to the same conclusion (WFC: PE Between Declarations). Adding a new patch which uses this for its check as opposed to just checking if it is a parameter entity. ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2004-02-13 00:01 Message: Logged In: YES user_id=290026 One more comment: It seems that Well-formedness constraint: PE Between Declarations applies here rather than section 4.3.2. I guess the solution might involve modifying the processInternalEntity() function in such a way, that the state before and after calling doProlog() is checked for two things: 1) is this a PE reference between declarations? 2) if yes, how does it return - any incomplete declarations? ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2004-02-12 22:39 Message: Logged In: YES user_id=290026 Well, the patch seems to fix the two test cases mentioned below, but when I ran Expat through the whole test suite again, it turned out that it now fails on 32 test cases more than before. One example: test case xmlconf/sun/valid/optional.xml uses the dtdtest.dtd in the same directory. It is well-formed and valid, but Expat now reports a syntax error on line 19, column 26 of the dtd. Seems this patch should be examined more closely. But I wouldn't give up yet. ---------------------------------------------------------------------- Comment By: Jeremy Kloth (jkloth) Date: 2004-02-12 21:28 Message: Logged In: YES user_id=38980 Attached is the "Fix Explained" (hopefully) document. ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2004-02-12 21:02 Message: Logged In: YES user_id=290026 OK, now I remember. If you look at bug #569461 there was a discussion regarding these two test cases, (a while back) and there I thought it would require some time to understand the logic in Expat well enough for a fix. This is cool - having a fix for that! Thanks! I would like you to explain the logic behind the fix, because I really don't want to "fix" Expat so short before a new release unless I understand the fix and can reasonably be sure it doesn't mess up anything else. You might want to create a "Fix Explained" attachment rather than a note, as this web interface really isn't a good text editor. ---------------------------------------------------------------------- Comment By: Jeremy Kloth (jkloth) Date: 2004-02-12 20:52 Message: Logged In: YES user_id=38980 Actually, the error should be on line 4 (the %e; expansion). I'm using a CVS (updated today) build. I've attached another invalid example to further demonstrate the problem. The XML Test Suite tests for this case are xmltest/not-wf/not-sa/010.xml and 011.xml ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2004-02-12 20:13 Message: Logged In: YES user_id=290026 I tried the current Expat (CVS), and it reports a syntax error on line 5, column 0 for bad.xml. Is that not what it should do? Are you saying that your copy of Expat doesn't do that? Which version are you using? Which test cases of the XML conformance suite does Expat not pass - related to this issue? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=896188&group_id=10127 From noreply at sourceforge.net Mon Feb 16 02:54:24 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Feb 16 02:55:28 2004 Subject: [Expat-bugs] [ expat-Bugs-897857 ] error compiling for windows with mingw Message-ID: Bugs item #897857, was opened at 2004-02-16 02:54 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=897857&group_id=10127 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Jason Short (jdorje) Assigned to: Nobody/Anonymous (nobody) Summary: error compiling for windows with mingw Initial Comment: I tried to compile CVS Expat for win32 using Mingw on Debian unstable (sid). Everything is up-to-date as of Feb 16. Mingw is a set of tools for cross-compiling programs targeted toward windows. The compilation is done on a non-windows machine (in this case a GNU/Linux box). I run the following sequence to do the compilation: export LD_LIBRARY_PATH=/usr/i586-mingw32msvc/lib export CC=i586-mingw32msvc-gcc export RANLIB=i586-mingw32msvc-ranlib export AR=i586-mingw32msvc-ar ./configure --host=i586-mingw32msvc make this works fine until the very end of the compilation, when I get this error: /bin/sh ./libtool --silent --mode=link i586-mingw32msvc-gcc -g -O2 -Wall -Wmissing-prototypes -Wstrict-prototypes -fexceptions -DHAVE_EXPAT_CONFIG_H -I./lib -I. -o xmlwf/xmlwf xmlwf/xmlwf.o xmlwf/xmlfile.o xmlwf/codepage.o xmlwf/readfilemap.o libexpat.la ./libtool: line 4921: .libs/lt-xmlwf/xmlwf.c: No such file or directory ./libtool: line 4937: .libs/lt-xmlwf/xmlwf.c: No such file or directory ./libtool: line 4996: .libs/lt-xmlwf/xmlwf.c: No such file or directory ./libtool: line 5000: .libs/lt-xmlwf/xmlwf.c: No such file or directory ./libtool: line 5010: .libs/lt-xmlwf/xmlwf.c: No such file or directory ./libtool: line 5014: .libs/lt-xmlwf/xmlwf.c: No such file or directory i586-mingw32msvc-gcc: .libs/lt-xmlwf/xmlwf.c: No such file or directory However compilation seems to complete all right. I now have a libexpat.la and the contents of .libs are: [jdorje@devon:~/src/expat]$ ls -la .libs/ total 1148 drwxr-xr-x 2 jdorje jdorje 4096 Feb 16 02:30 . drwxr-xr-x 14 jdorje jdorje 4096 Feb 16 02:30 .. -rwxr-xr-x 1 jdorje jdorje 706031 Feb 16 02:30 libexpat-0.dll -rw-r--r-- 1 jdorje jdorje 387146 Feb 16 02:30 libexpat.a -rw-r--r-- 1 jdorje jdorje 53002 Feb 16 02:30 libexpat.dll.a lrwxrwxrwx 1 jdorje jdorje 14 Feb 16 02:30 libexpat.la -> ../libexpat.la -rw-r--r-- 1 jdorje jdorje 790 Feb 16 02:30 libexpat.lai When I try to use the compiled library it works. I really have no idea what the error means or if it is important. I suspect there's an error in a Makefile.in somewhere causing it. Out of curiosity, why do you not use automake? jason short ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=897857&group_id=10127 From noreply at sourceforge.net Tue Feb 17 12:33:00 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Feb 17 13:19:35 2004 Subject: [Expat-bugs] [ expat-Bugs-898906 ] Expat fails to correctly parse content data Message-ID: Bugs item #898906, was opened at 2004-02-17 09:33 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=898906&group_id=10127 Category: www.libexpat.org Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Fred L. Drake, Jr. (fdrake) Summary: Expat fails to correctly parse content data Initial Comment: In the following XML file: if (x < y) the < in the attribute is correctly returned as "<", however, in the character block, it appears to be returned as a NULL. I will try to look into it to see if I can figure out where expat went wrong. Here is the output from my simple test app using expat: defaultHandler: ' Bugs item #899548, was opened at 2004-02-18 13:59 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=899548&group_id=10127 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Zygmunt Krynicki (zygoon) Assigned to: Nobody/Anonymous (nobody) Summary: Expat crashes and generates wrong resulst in XML_ParseBuffer Initial Comment: Identical code using XML_Parse works correctly. Expat version: 1.95.7 Backtrace: Program received signal SIGSEGV, Segmentation fault. 0x4003cb4e in normal_updatePosition (enc=0x40050260, ptr=0x804d000
, end=0x804baa0 "", pos=0x804a47c) at xmltok_impl.c:1745 (gdb) bt #0 0x4003cb4e in normal_updatePosition (enc=0x40050260, ptr=0x804d000
, end=0x804baa0 "", pos=0x804a47c) at xmltok_impl.c:1745 #1 0x4002ec29 in XML_GetCurrentColumnNumber (parser=0x804a2e8) at lib/xmlparse.c:1615 #2 0x08048e43 in main () #3 0x40069d06 in __libc_start_main () from /lib/libc.so.6 Code fragment with error checking snipped #define BUF_SIZE 4096 p = XML_ParserCreate (NULL); buffer = XML_GetBuffer (p, BUFF_SIZE); do { len = read (fd, buffer, BUFF_SIZE); if (len < 0) { fprintf (stdout, "%s: %s\n", *argv, strerror (errno)); break; } if (! XML_ParseBuffer (p, len, len == 0)) { fprintf (stdout, "%s:%d:%d %s\n", *argv, XML_GetCurrentLineNumber (p), XML_GetCurrentColumnNumber (p), XML_ErrorString (XML_GetErrorCode (p)) ); } } while (len > 0); The original xml is valid and parses without errors when I allocate the buffer myself and use XML_Parse ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=899548&group_id=10127 From noreply at sourceforge.net Wed Feb 18 10:51:22 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Feb 18 10:52:45 2004 Subject: [Expat-bugs] [ expat-Bugs-898906 ] Expat fails to correctly parse content data Message-ID: Bugs item #898906, was opened at 2004-02-17 12:33 Message generated for change (Comment added) made by kwaclaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=898906&group_id=10127 Category: www.libexpat.org Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Fred L. Drake, Jr. (fdrake) Summary: Expat fails to correctly parse content data Initial Comment: In the following XML file: if (x < y) the < in the attribute is correctly returned as "<", however, in the character block, it appears to be returned as a NULL. I will try to look into it to see if I can figure out where expat went wrong. Here is the output from my simple test app using expat: defaultHandler: 'Comment By: Karl Waclawek (kwaclaw) Date: 2004-02-18 10:51 Message: Logged In: YES user_id=290026 The way your document appears here is not well-formed, but maybe the HTML processing expanded some entities. Please attach the document as a file. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=898906&group_id=10127 From noreply at sourceforge.net Wed Feb 18 10:54:14 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Feb 18 10:55:38 2004 Subject: [Expat-bugs] [ expat-Bugs-899548 ] Expat crashes and generates wrong resulst in XML_ParseBuffer Message-ID: Bugs item #899548, was opened at 2004-02-18 07:59 Message generated for change (Comment added) made by kwaclaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=899548&group_id=10127 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Zygmunt Krynicki (zygoon) >Assigned to: Karl Waclawek (kwaclaw) Summary: Expat crashes and generates wrong resulst in XML_ParseBuffer Initial Comment: Identical code using XML_Parse works correctly. Expat version: 1.95.7 Backtrace: Program received signal SIGSEGV, Segmentation fault. 0x4003cb4e in normal_updatePosition (enc=0x40050260, ptr=0x804d000
, end=0x804baa0 "", pos=0x804a47c) at xmltok_impl.c:1745 (gdb) bt #0 0x4003cb4e in normal_updatePosition (enc=0x40050260, ptr=0x804d000
, end=0x804baa0 "", pos=0x804a47c) at xmltok_impl.c:1745 #1 0x4002ec29 in XML_GetCurrentColumnNumber (parser=0x804a2e8) at lib/xmlparse.c:1615 #2 0x08048e43 in main () #3 0x40069d06 in __libc_start_main () from /lib/libc.so.6 Code fragment with error checking snipped #define BUF_SIZE 4096 p = XML_ParserCreate (NULL); buffer = XML_GetBuffer (p, BUFF_SIZE); do { len = read (fd, buffer, BUFF_SIZE); if (len < 0) { fprintf (stdout, "%s: %s\n", *argv, strerror (errno)); break; } if (! XML_ParseBuffer (p, len, len == 0)) { fprintf (stdout, "%s:%d:%d %s\n", *argv, XML_GetCurrentLineNumber (p), XML_GetCurrentColumnNumber (p), XML_ErrorString (XML_GetErrorCode (p)) ); } } while (len > 0); The original xml is valid and parses without errors when I allocate the buffer myself and use XML_Parse ---------------------------------------------------------------------- >Comment By: Karl Waclawek (kwaclaw) Date: 2004-02-18 10:54 Message: Logged In: YES user_id=290026 Please attach a simple self-contained program (C source) that can reproduce this error. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=899548&group_id=10127 From noreply at sourceforge.net Wed Feb 18 10:55:32 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Feb 18 10:57:13 2004 Subject: [Expat-bugs] [ expat-Bugs-897857 ] error compiling for windows with mingw Message-ID: Bugs item #897857, was opened at 2004-02-16 02:54 Message generated for change (Comment added) made by kwaclaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=897857&group_id=10127 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Jason Short (jdorje) >Assigned to: Gerrit Haase (siebenschlaefer) Summary: error compiling for windows with mingw Initial Comment: I tried to compile CVS Expat for win32 using Mingw on Debian unstable (sid). Everything is up-to-date as of Feb 16. Mingw is a set of tools for cross-compiling programs targeted toward windows. The compilation is done on a non-windows machine (in this case a GNU/Linux box). I run the following sequence to do the compilation: export LD_LIBRARY_PATH=/usr/i586-mingw32msvc/lib export CC=i586-mingw32msvc-gcc export RANLIB=i586-mingw32msvc-ranlib export AR=i586-mingw32msvc-ar ./configure --host=i586-mingw32msvc make this works fine until the very end of the compilation, when I get this error: /bin/sh ./libtool --silent --mode=link i586-mingw32msvc-gcc -g -O2 -Wall -Wmissing-prototypes -Wstrict-prototypes -fexceptions -DHAVE_EXPAT_CONFIG_H -I./lib -I. -o xmlwf/xmlwf xmlwf/xmlwf.o xmlwf/xmlfile.o xmlwf/codepage.o xmlwf/readfilemap.o libexpat.la ./libtool: line 4921: .libs/lt-xmlwf/xmlwf.c: No such file or directory ./libtool: line 4937: .libs/lt-xmlwf/xmlwf.c: No such file or directory ./libtool: line 4996: .libs/lt-xmlwf/xmlwf.c: No such file or directory ./libtool: line 5000: .libs/lt-xmlwf/xmlwf.c: No such file or directory ./libtool: line 5010: .libs/lt-xmlwf/xmlwf.c: No such file or directory ./libtool: line 5014: .libs/lt-xmlwf/xmlwf.c: No such file or directory i586-mingw32msvc-gcc: .libs/lt-xmlwf/xmlwf.c: No such file or directory However compilation seems to complete all right. I now have a libexpat.la and the contents of .libs are: [jdorje@devon:~/src/expat]$ ls -la .libs/ total 1148 drwxr-xr-x 2 jdorje jdorje 4096 Feb 16 02:30 . drwxr-xr-x 14 jdorje jdorje 4096 Feb 16 02:30 .. -rwxr-xr-x 1 jdorje jdorje 706031 Feb 16 02:30 libexpat-0.dll -rw-r--r-- 1 jdorje jdorje 387146 Feb 16 02:30 libexpat.a -rw-r--r-- 1 jdorje jdorje 53002 Feb 16 02:30 libexpat.dll.a lrwxrwxrwx 1 jdorje jdorje 14 Feb 16 02:30 libexpat.la -> ../libexpat.la -rw-r--r-- 1 jdorje jdorje 790 Feb 16 02:30 libexpat.lai When I try to use the compiled library it works. I really have no idea what the error means or if it is important. I suspect there's an error in a Makefile.in somewhere causing it. Out of curiosity, why do you not use automake? jason short ---------------------------------------------------------------------- >Comment By: Karl Waclawek (kwaclaw) Date: 2004-02-18 10:55 Message: Logged In: YES user_id=290026 Assigned to Gerrit - this seems close to Cygwin. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=897857&group_id=10127 From noreply at sourceforge.net Wed Feb 18 11:16:27 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Feb 18 11:17:53 2004 Subject: [Expat-bugs] [ expat-Bugs-899548 ] Expat crashes and generates wrong resulst in XML_ParseBuffer Message-ID: Bugs item #899548, was opened at 2004-02-18 07:59 Message generated for change (Comment added) made by kwaclaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=899548&group_id=10127 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Zygmunt Krynicki (zygoon) Assigned to: Karl Waclawek (kwaclaw) Summary: Expat crashes and generates wrong resulst in XML_ParseBuffer Initial Comment: Identical code using XML_Parse works correctly. Expat version: 1.95.7 Backtrace: Program received signal SIGSEGV, Segmentation fault. 0x4003cb4e in normal_updatePosition (enc=0x40050260, ptr=0x804d000
, end=0x804baa0 "", pos=0x804a47c) at xmltok_impl.c:1745 (gdb) bt #0 0x4003cb4e in normal_updatePosition (enc=0x40050260, ptr=0x804d000
, end=0x804baa0 "", pos=0x804a47c) at xmltok_impl.c:1745 #1 0x4002ec29 in XML_GetCurrentColumnNumber (parser=0x804a2e8) at lib/xmlparse.c:1615 #2 0x08048e43 in main () #3 0x40069d06 in __libc_start_main () from /lib/libc.so.6 Code fragment with error checking snipped #define BUF_SIZE 4096 p = XML_ParserCreate (NULL); buffer = XML_GetBuffer (p, BUFF_SIZE); do { len = read (fd, buffer, BUFF_SIZE); if (len < 0) { fprintf (stdout, "%s: %s\n", *argv, strerror (errno)); break; } if (! XML_ParseBuffer (p, len, len == 0)) { fprintf (stdout, "%s:%d:%d %s\n", *argv, XML_GetCurrentLineNumber (p), XML_GetCurrentColumnNumber (p), XML_ErrorString (XML_GetErrorCode (p)) ); } } while (len > 0); The original xml is valid and parses without errors when I allocate the buffer myself and use XML_Parse ---------------------------------------------------------------------- >Comment By: Karl Waclawek (kwaclaw) Date: 2004-02-18 11:16 Message: Logged In: YES user_id=290026 Looking closer at your code: You must call XML_GetBuffer before *each* call to XML_ParseBuffer, as this updates internal pointers and moves unprocessed input data inside the buffer and also potentially reallocates the buffer. ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2004-02-18 10:54 Message: Logged In: YES user_id=290026 Please attach a simple self-contained program (C source) that can reproduce this error. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=899548&group_id=10127 From noreply at sourceforge.net Thu Feb 19 05:08:45 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Feb 19 05:10:39 2004 Subject: [Expat-bugs] [ expat-Bugs-899548 ] Expat crashes and generates wrong resulst in XML_ParseBuffer Message-ID: Bugs item #899548, was opened at 2004-02-18 13:59 Message generated for change (Comment added) made by zygoon You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=899548&group_id=10127 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Zygmunt Krynicki (zygoon) Assigned to: Karl Waclawek (kwaclaw) Summary: Expat crashes and generates wrong resulst in XML_ParseBuffer Initial Comment: Identical code using XML_Parse works correctly. Expat version: 1.95.7 Backtrace: Program received signal SIGSEGV, Segmentation fault. 0x4003cb4e in normal_updatePosition (enc=0x40050260, ptr=0x804d000
, end=0x804baa0 "", pos=0x804a47c) at xmltok_impl.c:1745 (gdb) bt #0 0x4003cb4e in normal_updatePosition (enc=0x40050260, ptr=0x804d000
, end=0x804baa0 "", pos=0x804a47c) at xmltok_impl.c:1745 #1 0x4002ec29 in XML_GetCurrentColumnNumber (parser=0x804a2e8) at lib/xmlparse.c:1615 #2 0x08048e43 in main () #3 0x40069d06 in __libc_start_main () from /lib/libc.so.6 Code fragment with error checking snipped #define BUF_SIZE 4096 p = XML_ParserCreate (NULL); buffer = XML_GetBuffer (p, BUFF_SIZE); do { len = read (fd, buffer, BUFF_SIZE); if (len < 0) { fprintf (stdout, "%s: %s\n", *argv, strerror (errno)); break; } if (! XML_ParseBuffer (p, len, len == 0)) { fprintf (stdout, "%s:%d:%d %s\n", *argv, XML_GetCurrentLineNumber (p), XML_GetCurrentColumnNumber (p), XML_ErrorString (XML_GetErrorCode (p)) ); } } while (len > 0); The original xml is valid and parses without errors when I allocate the buffer myself and use XML_Parse ---------------------------------------------------------------------- >Comment By: Zygmunt Krynicki (zygoon) Date: 2004-02-19 11:08 Message: Logged In: YES user_id=927776 The bug goes away when I move XML_GetBuffer inside the read loop. I assume the code fragment is irrelevant now Thank you for your quick response. ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2004-02-18 17:16 Message: Logged In: YES user_id=290026 Looking closer at your code: You must call XML_GetBuffer before *each* call to XML_ParseBuffer, as this updates internal pointers and moves unprocessed input data inside the buffer and also potentially reallocates the buffer. ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2004-02-18 16:54 Message: Logged In: YES user_id=290026 Please attach a simple self-contained program (C source) that can reproduce this error. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=899548&group_id=10127 From noreply at sourceforge.net Thu Feb 19 09:00:12 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Feb 19 10:03:36 2004 Subject: [Expat-bugs] [ expat-Bugs-899548 ] Expat crashes and generates wrong resulst in XML_ParseBuffer Message-ID: Bugs item #899548, was opened at 2004-02-18 07:59 Message generated for change (Settings changed) made by kwaclaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=899548&group_id=10127 Category: None Group: None >Status: Closed >Resolution: Rejected Priority: 5 Submitted By: Zygmunt Krynicki (zygoon) Assigned to: Karl Waclawek (kwaclaw) Summary: Expat crashes and generates wrong resulst in XML_ParseBuffer Initial Comment: Identical code using XML_Parse works correctly. Expat version: 1.95.7 Backtrace: Program received signal SIGSEGV, Segmentation fault. 0x4003cb4e in normal_updatePosition (enc=0x40050260, ptr=0x804d000
, end=0x804baa0 "", pos=0x804a47c) at xmltok_impl.c:1745 (gdb) bt #0 0x4003cb4e in normal_updatePosition (enc=0x40050260, ptr=0x804d000
, end=0x804baa0 "", pos=0x804a47c) at xmltok_impl.c:1745 #1 0x4002ec29 in XML_GetCurrentColumnNumber (parser=0x804a2e8) at lib/xmlparse.c:1615 #2 0x08048e43 in main () #3 0x40069d06 in __libc_start_main () from /lib/libc.so.6 Code fragment with error checking snipped #define BUF_SIZE 4096 p = XML_ParserCreate (NULL); buffer = XML_GetBuffer (p, BUFF_SIZE); do { len = read (fd, buffer, BUFF_SIZE); if (len < 0) { fprintf (stdout, "%s: %s\n", *argv, strerror (errno)); break; } if (! XML_ParseBuffer (p, len, len == 0)) { fprintf (stdout, "%s:%d:%d %s\n", *argv, XML_GetCurrentLineNumber (p), XML_GetCurrentColumnNumber (p), XML_ErrorString (XML_GetErrorCode (p)) ); } } while (len > 0); The original xml is valid and parses without errors when I allocate the buffer myself and use XML_Parse ---------------------------------------------------------------------- >Comment By: Karl Waclawek (kwaclaw) Date: 2004-02-19 09:00 Message: Logged In: YES user_id=290026 Yes, no example needed. The documentation for XML_GetBuffer does describe this requirement, btw. Closed report - not a bug. ---------------------------------------------------------------------- Comment By: Zygmunt Krynicki (zygoon) Date: 2004-02-19 05:08 Message: Logged In: YES user_id=927776 The bug goes away when I move XML_GetBuffer inside the read loop. I assume the code fragment is irrelevant now Thank you for your quick response. ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2004-02-18 11:16 Message: Logged In: YES user_id=290026 Looking closer at your code: You must call XML_GetBuffer before *each* call to XML_ParseBuffer, as this updates internal pointers and moves unprocessed input data inside the buffer and also potentially reallocates the buffer. ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2004-02-18 10:54 Message: Logged In: YES user_id=290026 Please attach a simple self-contained program (C source) that can reproduce this error. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=899548&group_id=10127 From noreply at sourceforge.net Sun Feb 22 03:43:13 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Feb 22 03:45:02 2004 Subject: [Expat-bugs] [ expat-Bugs-897857 ] error compiling for windows with mingw Message-ID: Bugs item #897857, was opened at 2004-02-16 08:54 Message generated for change (Comment added) made by siebenschlaefer You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=897857&group_id=10127 >Category: Build control >Group: Third-party Bug >Status: Closed Resolution: None Priority: 5 Submitted By: Jason Short (jdorje) Assigned to: Gerrit Haase (siebenschlaefer) Summary: error compiling for windows with mingw Initial Comment: I tried to compile CVS Expat for win32 using Mingw on Debian unstable (sid). Everything is up-to-date as of Feb 16. Mingw is a set of tools for cross-compiling programs targeted toward windows. The compilation is done on a non-windows machine (in this case a GNU/Linux box). I run the following sequence to do the compilation: export LD_LIBRARY_PATH=/usr/i586-mingw32msvc/lib export CC=i586-mingw32msvc-gcc export RANLIB=i586-mingw32msvc-ranlib export AR=i586-mingw32msvc-ar ./configure --host=i586-mingw32msvc make this works fine until the very end of the compilation, when I get this error: /bin/sh ./libtool --silent --mode=link i586-mingw32msvc-gcc -g -O2 -Wall -Wmissing-prototypes -Wstrict-prototypes -fexceptions -DHAVE_EXPAT_CONFIG_H -I./lib -I. -o xmlwf/xmlwf xmlwf/xmlwf.o xmlwf/xmlfile.o xmlwf/codepage.o xmlwf/readfilemap.o libexpat.la ./libtool: line 4921: .libs/lt-xmlwf/xmlwf.c: No such file or directory ./libtool: line 4937: .libs/lt-xmlwf/xmlwf.c: No such file or directory ./libtool: line 4996: .libs/lt-xmlwf/xmlwf.c: No such file or directory ./libtool: line 5000: .libs/lt-xmlwf/xmlwf.c: No such file or directory ./libtool: line 5010: .libs/lt-xmlwf/xmlwf.c: No such file or directory ./libtool: line 5014: .libs/lt-xmlwf/xmlwf.c: No such file or directory i586-mingw32msvc-gcc: .libs/lt-xmlwf/xmlwf.c: No such file or directory However compilation seems to complete all right. I now have a libexpat.la and the contents of .libs are: [jdorje@devon:~/src/expat]$ ls -la .libs/ total 1148 drwxr-xr-x 2 jdorje jdorje 4096 Feb 16 02:30 . drwxr-xr-x 14 jdorje jdorje 4096 Feb 16 02:30 .. -rwxr-xr-x 1 jdorje jdorje 706031 Feb 16 02:30 libexpat-0.dll -rw-r--r-- 1 jdorje jdorje 387146 Feb 16 02:30 libexpat.a -rw-r--r-- 1 jdorje jdorje 53002 Feb 16 02:30 libexpat.dll.a lrwxrwxrwx 1 jdorje jdorje 14 Feb 16 02:30 libexpat.la -> ../libexpat.la -rw-r--r-- 1 jdorje jdorje 790 Feb 16 02:30 libexpat.lai When I try to use the compiled library it works. I really have no idea what the error means or if it is important. I suspect there's an error in a Makefile.in somewhere causing it. Out of curiosity, why do you not use automake? jason short ---------------------------------------------------------------------- >Comment By: Gerrit Haase (siebenschlaefer) Date: 2004-02-22 09:43 Message: Logged In: YES user_id=76037 Libtool is somewhat broken, i.e. when automake is not used. Try this patch to ltmain.sh (also attached to save the format): $ diff -ud ltmain.sh~ ltmain.sh --- ltmain.sh~ 2003-08-18 07:36:11.001000000 +0200 +++ ltmain.sh 2003-10-30 00:13:30.104377600 +0100 @@ -4481,8 +4481,10 @@ esac case $host in *cygwin* | *mingw* ) - cwrappersource=`$echo ${objdir}/lt-${output}.c` - cwrapper=`$echo ${output}.exe` + output_name=`basename $output` + output_path=`dirname $output` + cwrappersource=`$echo ${output_path}/${objdir}/lt-${output_name}.c` + cwrapper=`$echo ${output_path}/${output_name}.exe` $rm $cwrappersource $cwrapper trap "$rm $cwrappersource $cwrapper; exit 1" 1 2 15 @@ -4813,7 +4815,7 @@ # are only useful if you want to execute the "real" binary. # Since the "real" binary is built for $host, then this # wrapper might as well be built for $host, too. - $run $LTCC -s -o $cwrapper $cwrappersource + $run ln -f ${output_path}/${objdir}/${output_name}.exe ${cwrapper} ;; esac $rm $output ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2004-02-18 16:55 Message: Logged In: YES user_id=290026 Assigned to Gerrit - this seems close to Cygwin. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=897857&group_id=10127 From ya.news at wanadoo.fr Sat Feb 21 03:28:11 2004 From: ya.news at wanadoo.fr (ya.news) Date: Sun Feb 22 11:51:37 2004 Subject: [Expat-bugs] French accents error Message-ID: <000a01c3f854$a46a3130$34910f50@lysapc> Hello everybody I?m using Expat PocketPC version ported by mov software (http://www.movsoftware.com/expatxml.htm) and I have a problem with special characters at a specific place. My XML data looks like this : ?? ? The Expat always stops at ? (error message : ?Not well formed?). If I either change "?" for an "u" it works fine. I tried to replace UTF-8 by iso-8859-1 with no success. Any help please ? Thanks lot in advance -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.libexpat.org/pipermail/expat-bugs/attachments/20040221/c0f0ebf7/attachment.html From noreply at sourceforge.net Wed Feb 25 11:20:44 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Feb 25 11:23:09 2004 Subject: [Expat-bugs] [ expat-Bugs-898906 ] Expat fails to correctly parse content data Message-ID: Bugs item #898906, was opened at 2004-02-17 17:33 Message generated for change (Comment added) made by nhendricks You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=898906&group_id=10127 Category: www.libexpat.org Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Fred L. Drake, Jr. (fdrake) Summary: Expat fails to correctly parse content data Initial Comment: In the following XML file: if (x < y) the < in the attribute is correctly returned as "<", however, in the character block, it appears to be returned as a NULL. I will try to look into it to see if I can figure out where expat went wrong. Here is the output from my simple test app using expat: defaultHandler: ' Bugs item #898906, was opened at 2004-02-17 17:33 Message generated for change (Comment added) made by nhendricks You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=898906&group_id=10127 Category: www.libexpat.org Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Fred L. Drake, Jr. (fdrake) Summary: Expat fails to correctly parse content data Initial Comment: In the following XML file: if (x < y) the < in the attribute is correctly returned as "<", however, in the character block, it appears to be returned as a NULL. I will try to look into it to see if I can figure out where expat went wrong. Here is the output from my simple test app using expat: defaultHandler: ' Bugs item #898906, was opened at 2004-02-17 12:33 Message generated for change (Comment added) made by kwaclaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=898906&group_id=10127 Category: www.libexpat.org Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Fred L. Drake, Jr. (fdrake) Summary: Expat fails to correctly parse content data Initial Comment: In the following XML file: if (x < y) the < in the attribute is correctly returned as "<", however, in the character block, it appears to be returned as a NULL. I will try to look into it to see if I can figure out where expat went wrong. Here is the output from my simple test app using expat: defaultHandler: 'Comment By: Karl Waclawek (kwaclaw) Date: 2004-02-25 11:32 Message: Logged In: YES user_id=290026 One thing that comes to mind: There are two ways of setting a default handler. One of them suppresses reporting of internal entitities. Please check the docs and compare with your code. ---------------------------------------------------------------------- Comment By: Nicholas hendricks (nhendricks) Date: 2004-02-25 11:24 Message: Logged In: YES user_id=977364 Make that a < where the < is. I didn't realize sourceforce would parse the comments, instead of including them as plain text. ---------------------------------------------------------------------- Comment By: Nicholas hendricks (nhendricks) Date: 2004-02-25 11:20 Message: Logged In: YES user_id=977364 I am a sourceforce NOOB, so I cant figure out how to attach files. The < in the above example should be < ---------------------------------------------------------------------- Comment By: Karl Waclawek (kwaclaw) Date: 2004-02-18 10:51 Message: Logged In: YES user_id=290026 The way your document appears here is not well-formed, but maybe the HTML processing expanded some entities. Please attach the document as a file. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110127&aid=898906&group_id=10127