Re: Memory access bug in XMLString2Perl()
Chris Cheung <[email protected]>
| Newsgroups | gmane.text.xml.xerces-p.devel |
|---|---|
| Message-ID | <Pine.LNX.4.44.0312211746400.3204-100000@mars.cluster.clc.cuhk.edu.hk> |
On 20 Dec 2003, Jason E. Stewart wrote: > > The memory to malloc should be (length * UTF8_MAXLEN + 1): > > > > XMLByte* res = new XMLByte[length * UTF8_MAXLEN + 1]; // output > > > > so that the memory for the ending '\0' is not missed. > > Does changing this make a difference? I would be surprised - the call > to transcode to gives the *maximum possible length* for the buffer, > and returns the *actual* length used. Does changing this make valgrind > happy? I've got no objection to adding this to the code, I'm just > curious. Yes. After I changed the length, recompile and perform the same test, the error message from valgrind disappear. Will this issue be fixed in the next release? > > Cheers, > jas. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > -- Best Regards, Chris Cheung Center for Large-Scale Computation Have a nice day!