On Mon, Mar 26, 2012 at 05:42:56PM -0500, Yarin <[email protected]> wrote:
> Upon investigation I found that it was a string _not_ being properly null
> terminated (in spite of the man page suggesting that it might be done
> automatically). The fix for this is quite simple...
Hmm, if that were the case, mbstowcs would use more than one wide
character per input octet - under what conditions would this legally
happen?
(does openbsd support __STDC_ISO_10646__? urxvt requires this).
> need to be replaced with
that would also corrupt data in that case - if the buffer is not big
enough, data is lost.
> While I understand this bug may or may not be present on a system depending
> on it's implementation of mbstowcs(), it is still a very legitimate bug.
yes, but it sounds as if the bug is in mbstowcs itself.
--
The choice of a Deliantra, the free code+content MORPG
-----==- _GNU_ http://www.deliantra.net
----==-- _ generation
---==---(_)__ __ ____ __ Marc Lehmann
--==---/ / _ \/ // /\ \/ / [email protected]
-=====/_/_//_/\_,_/ /_/\_\
_______________________________________________
rxvt-unicode mailing list
[email protected]
http://lists.schmorp.de/cgi-bin/mailman/listinfo/rxvt-unicode
