Open GoogleCodeExporter opened 9 years ago
To clarify, the bug is due to the fact that the 'direct' and 'mux' types are
mixed, instead of grouped. Mixing will not always cause the bug - only certain
orderings will do so.
This is a known issue in past versions of ezxml.
Original comment by jeffrey....@gmail.com
on 8 May 2012 at 12:48
Actually, I mistakenly thought I tested with the new ezxml. In fact I did not.
I didn't realize we had modified the ezxml.c file. Perhaps our modifications
are the source of the bug. Diffing the latest version of ezxml with our
version, I only notice the locations that we have changed.
For now we should just be careful in how we write architecture files.
Original comment by jeffrey....@gmail.com
on 8 May 2012 at 6:44
When I get the newest ezxml, add in the line numbers update, and run, it seg
faults. Will probably need to do what Ted Campbell did to fix the numerous
memory access bugs in ezxml if we want to use the newest version.
Original comment by JasonKai...@gmail.com
on 9 May 2012 at 8:23
Original issue reported on code.google.com by
jeffrey....@gmail.com
on 8 May 2012 at 12:46