Subject: more iconv trouble
From: Mike Nordell (tamlin@algonet.se)
Date: Thu Nov 09 2000 - 14:56:54 CST
While trying to sort out the 8859-15/1 trouble, I simply changed the string
in iconv to read "8859-1". The led to a crash (segv) in
wvConvertUnicodeToiso8859_15 since neither inbytesleft nor outbytesleft
contained legal values. It got called from try_UToC() in
xap_EncodingManager.cpp(244) like
iconv(iconv_handle,NULL,NULL,NULL,NULL);
Well, that explains that crash. :-)
Now, is zero pointers legal input values to the function iconv()? If they
are, shouldn't its "child" functions check what data they try to operate on?
If a zero pointer is indeed illegal, shouldn't the function iconv() assert
the parameters validness?
/Mike (oh, forgot in my last post, please don't cc)
This archive was generated by hypermail 2b25 : Thu Nov 09 2000 - 14:55:38 CST