Well, the reported stack-overflow looks like an issue in the iconv_open() implementation; the function is supposed to receive two arbitrary C strings, but apparently can't handle very long C strings. But even if some iconv_open() implementation documents a maximum length, that should be handled by the calling code, i.e. libxml2. Of course, we could restrict the length, but what should be the limit?

Well, the reported stack-overflow looks like an issue in the iconv_open() implementation; the function is supposed to receive two arbitrary C strings, but apparently can't handle very long C strings. But even if some iconv_open() implementation documents a maximum length, that should be handled by the calling code, i.e. libxml2. Of course, we could restrict the length, but what should be the limit?

Oh, I do agree that this is not our problem and we shouldn't address it from our side. Just saying that this fix isn't really related to that issue...

Well, would have been better to close that ticket as not a bug, and to open a new one regarding the NUL bytes, but I think it has been okay-ish to "retarget" the ticket.