Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 6 Mar 2016 16:19:10 -0500
From:      Pedro Giffuni <pfg@FreeBSD.org>
To:        Baptiste Daroussin <bapt@FreeBSD.org>, Roman Bogorodskiy <novel@FreeBSD.org>
Cc:        freebsd-current@freebsd.org
Subject:   Re: lldb input issue
Message-ID:  <56DC9ECE.5000707@FreeBSD.org>
In-Reply-To: <56DC911D.7050909@FreeBSD.org>
References:  <56dc5e77.c53d700a.262e9.ffff953d@mx.google.com> <20160306172550.GL31877@ivaldir.etoilebsd.net> <56dc8b32.01a0700a.6dc13.121c@mx.google.com> <20160306200549.GM31877@ivaldir.etoilebsd.net> <56DC911D.7050909@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help


On 03/06/16 15:20, Pedro Giffuni wrote:
>
>
> El 06/03/2016 a las 15:05, Baptiste Daroussin escribió:
>> On Sun, Mar 06, 2016 at 10:55:27PM +0300, Roman Bogorodskiy wrote:
>>>    Baptiste Daroussin wrote:
>>>
>>>> On Sun, Mar 06, 2016 at 07:44:34PM +0300, Roman Bogorodskiy wrote:
>>>>> Hi,
>>>>>
>>>>> I'm seeing an issue with lldb: when I start it (without arguments) and
>>>>> try to type commands, it looks like this:
>>>>>
>>>>> $  lldb
>>>>> (lldb) \U+7F68\U+7F65\U+7F6C\U+7F70\U+7F0A
>>>>>
>>>>> So, basically, I cannot execute any command and cannot even exit from
>>>>> its shell, only by ctrl-z and killing it.
>>>>>
>>>>> This happens to me on today's -CURRENT / amd64.
>>>>>
>>>>> I was wondering if that's an issue with my user's locale, but the
>>>>> behavior is same for root.
>>>>>
>>>>> Also, I can see exactly the same behavior with lldb on FreeBSD.
>>>                                                             ^^^^^^^
>>> Oops, that's supposed to be 'freefall'.
>>>
>>>>> Is that some known issue or maybe configuration problem?
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Roman Bogorodskiy
>>>>
>>>>
>>>> Sounds like an issue with libedit, probably due to the latest import
>>>> of libedit
>>>> (just a guess)
>>> It could be. BTW, I've installed lldb38 using pkg and it works fine.
>>>
>> Which is linked to libedit from ports (older that in base) so it seems
>> to prove
>> that libedit update might be the issue there.
>
> Hmm ... most of the changes were cosmetical. I will take a look though.
>

Actually we have had two updates lately with sufficient changes that it
is not easy to find which may be the culprit. I will revert the last
change in the hope that it is enough.

Sorry about this.

Pedro.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?56DC9ECE.5000707>