[lldb-dev] [Bug 28178] lldb segfault when debugging mysql in certain functions

https://llvm.org/bugs/show_bug.cgi?id=28178 Jeff Davis changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[lldb-dev] [3.9 Release] We have branched

Dear everyone, The 3.9 branch was created earlier today from trunk at r275826, after which the trunk version was bumped to 4.0.0. Release blockers for 3.9 are tracked by http://llvm.org/PR28600 Please mark any bugs (new or already tracked) that you think need to be fixed before the release as blo

Re: [lldb-dev] Typing in lldb is broken

The bug seems to be in lldb. However, I made lldb work again by downgrading libedit. I got that idea from a bug report for this issue at archlinux bugzilla. Thank you all On Tue, 19 Jul 2016 at 12:20 AM, Kate Stone wrote: > Agreed. LLDB uses some odd tricks in order to coerce libedit into > dis

Re: [lldb-dev] No event generated after a SBThread::JumpToLine() call

JumpToLine just resets the PC, it doesn't continue the process. For an API, it makes more sense to let the API user decide whether they want to do more work before continuing. So you wouldn't expect a "running" event. We could send a PC-changed event, but we generally only send that sort of ev

Re: [lldb-dev] Typing in lldb is broken

Agreed. LLDB uses some odd tricks in order to coerce libedit into displaying a different colored prompt, so these extra characters are doubtless a symptom of attempting to use ANSI cursor movement that is being misinterpreted by your terminal emulation. Kate Stone k8st...@apple.com

[lldb-dev] No event generated after a SBThread::JumpToLine() call

Hello everyone, After calling SBThread::JumpToLine(...) I was expecting that the thread would broadcast an event but it seems that this doesn't happen. Is this the intended behavior? Does the call to JumpToLine comes in pair with another function call? Regards, Marius Marius Trandafir Staff

Re: [lldb-dev] Typing in lldb is broken

Hi, This is probably some interaction between LLDB *and* your terminal. Hard to say why without knowing your environment. Could you check how is your terminal configured (unicode yes/no, which emulation mode, codepage, ...). Also try running "env" in your terminal and check for anything out of pla