Closed GoogleCodeExporter closed 9 years ago
This issue is related to axis2c-unofficial.
It was introduced in 5a45fe1784b5:
https://code.google.com/p/axis2c-unofficial/source/detail?r=5a45fe1784b541b8cabb
255a1c49e5af7bd12495
To workaround roll-back to previous changeset, compile and install
axis2c-unofficial by entering those commands:
hg up -rc1e885257106
make && make install
After that you shouldn't see crash.
Original comment by loentar
on 12 Oct 2013 at 6:13
I commited patch that fixes axis2c-unofficial, please update to latest
changeset (77b54e8f4b2a).
Original comment by loentar
on 12 Oct 2013 at 5:00
Hi Dmitry, I tried to reproduce the crash but was unable to...
I've just looked at the last changeset, saw that you reverted the code that
provoked the crash, but saw that you also made some other modifications in
guththila_xml_parser.c I didn't had the time to analyse those modifications
yet, does it still fix the issue of the modified buffer?
Original comment by alexmantaut
on 12 Oct 2013 at 11:07
Yes it fixes. Source buffer wouldn't get modified. Now Guththila only start
unescaping symbols when you get element value or attribute value in the copy of
the buffer.
To reproduce the issue see my description on
https://issues.apache.org/jira/browse/AXIS2C-1628 . There is a test service
which uses axiom_build_node_from_buffer.
One bad thing I see in your code: you allocating buffer using C runtime
(strdup()), but deallocating it using Axis2c runtime (AXIS2_FREE() not free()).
Not sure if it can cause problems.
This issue is not reproducible under valgrind (but reproducible under gdb).
That means the problem could be a race condition.
Original comment by loentar
on 13 Oct 2013 at 8:08
Hi Dmitry,
I couldn't reproduce the bug, not even with the tests attached to
AXIS2C-1628... I compiled it with/without optimization and runned it alone, in
gdb and valgrind and the error did not ocurr in my pc :(
Either way, David can you confirm that the patch solved the issue for you? If
it did I'll just commit the patch to trunk.
Original comment by alexmantaut
on 15 Oct 2013 at 2:18
Original issue reported on code.google.com by
davidb...@gmail.com
on 7 Oct 2013 at 12:24Attachments: