Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2002-April/023007.html below:

[Python-Dev] Regression in unicodestr.encode()?

• Previous message: [Python-Dev] Regression in unicodestr.encode()?
• Next message: [Python-Dev] Regression in unicodestr.encode()?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

"Martin v. Loewis" wrote:
> 
> "M.-A. Lemburg" <mal@lemburg.com> writes:
> 
> > Some debugging with gdb indicates that the codec is indeed writing
> > the 'nd', but the final _PyString_Resize() (which allocates a new
> > buffer and copies the data into that buffer) fails to copy the last
> > two characters from the string or overwrites it with NULLs.
> >
> > Looks like a pymalloc problem to me. Tim ?
> 
> It's a UTF-8 codec bug. The codec writes over the end of the buffer,
> then invokes resize. Resizing only copies the allocated bytes, hence
> the uninitialized bytes at the end.

Ah, yes, you're right.

-- 
Marc-Andre Lemburg
CEO eGenix.com Software GmbH
______________________________________________________________________
Company & Consulting:                           http://www.egenix.com/
Python Software:                   http://www.egenix.com/files/python/

• Previous message: [Python-Dev] Regression in unicodestr.encode()?
• Next message: [Python-Dev] Regression in unicodestr.encode()?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4