5

I installed a fresh copy of lldb on my machine. Anything typed after lldb makes its first output (in this case being error: empty command) turns into unicode literals. These unicode literals are recognised by lldb as empty commands. lldb This does not happen with gdb or python: gdb

Improve this question
3
  • Having same problem, not sure why.. :(
    – ioquatix
    Jul 16, 2016 at 5:49
  • Are you guys on ArchLinux? I, among others, have this bug in the most recent update to lldb 3.8.0 see the report
    – user154559
    Jul 23, 2016 at 13:05
  • After following comments from Arch bug report, I reported this in lldb bug tracking (Sorry, not enough rep for a comment)
    – phcerdan
    Aug 8, 2016 at 4:29

1 Answer 1

Reset to default
1

It seems like that this is a bug and is fixed in lldb 3.9.0.enter image description here

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .