<html><body><p><tt><font size="2">christos@zoulas.com (Christos Zoulas) wrote on 30.05.2017 17:46:58:<br><br>> I am sorry to say that this is my fault and this sucks. I accepted<br>> some patches that broke binary compatibility in a way that it is not<br>> user visible. Basically you seem to have version of libedit that is<br>> between the narrow one that works, and the wide one that has the<br>> binary compatibility of the wide code removed.<br>> <br>> | I managed to debug a bit myself, and I think the problem is this:<br>> <br>> Yes, this is correct. Basically your version of libedit handles<br>> properly the narrow char read function and breaks if it is defined<br>> as a wide char. if your histedit header does not have EL_ALIAS_TEXT<br>> defined, you can check for that define too and not use the wide read<br>> if that is not defined. Unfortunately there was no other change in<br>> the version that would help differentiating the two libedit versions.<br>> <br>> To fix this properly we would require an updated version of libedit.<br></font></tt><br><tt><font size="2">Hmm, from looking at the version of libedit I'm using it would</font></tt><br><tt><font size="2">appear that it should correctly handle either:</font></tt><br><tt><font size="2">- a narrow char read function installed via el_set; or</font></tt><br><tt><font size="2">- a wide char read function installed via el_wset</font></tt><br><tt><font size="2">which seems reasonable to me at first glance.</font></tt><br><br><tt><font size="2">However, LLDB currently uses a wide char read function but installs</font></tt><br><tt><font size="2">it with el_set, which is what breaks. This would seem to be rather</font></tt><br><tt><font size="2">a LLDB problem, or am I missing something?</font></tt><br><br><tt><font size="2">Bye,</font></tt><br><tt><font size="2">Ulrich</font></tt><br><BR>
</body></html>