|
| From: | Richard Frith-Macdonald |
| Subject: | [bug #28939] -[NSString getCString:] doesn't work |
| Date: | Sun, 21 Feb 2010 06:40:11 +0000 |
| User-agent: | Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6_2; en-us) AppleWebKit/531.21.8 (KHTML, like Gecko) Version/4.0.4 Safari/531.21.10 |
Update of bug #28939 (project gnustep):
Status: Need Info => Fixed
Open/Closed: Open => Closed
_______________________________________________________
Follow-up Comment #7:
Great ... that extra info was sufficient to reproduce the problem and fix
it.
The actual problem was an incorrectly initialised zone pointer when
converting the constant string to the UTF8 encoding (not an issue if you are
using latin1) ... which was causing memory allocation issues.
I have fixed that in svn trunk.
The same bug occurs for -getCString:maxLength:encoding: so using that is
*not* a reliable workaround.
Using the -cString or -dataUsingEncoding: methods would work around the
problem safely though.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?28939>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
| [Prev in Thread] | Current Thread | [Next in Thread] |