I'm using vscode and CodeLLDB to debug rust code.
```text
Internal debugger error:
Traceback (most recent call last):
File
"/home/joey/.vscode/extensions/vadimcn.vscode-lldb-1.2.3/adapter/debugsession.py",
line 1366, in handle_message
result = handler(args)
File
"/home/joey/.vscode/extensi
https://bugs.llvm.org/show_bug.cgi?id=20466
Jonas Devlieghere changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://bugs.llvm.org/show_bug.cgi?id=40189
Jonas Devlieghere changed:
What|Removed |Added
CC||jdevliegh...@apple.com
Resolution|-
We'll be at Tied House as usual, starting on Thursday the 1st at 7pm!
If you can, help us plan and RSVP here:
https://www.meetup.com/LLVM-Bay-Area-Social/events/kncsjlyzlbcb/
See everyone there!
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://
On 26/07/2019 20:43, Jim Ingham wrote:
Amplifying Fred's comments:
Most of the code in ParseSymtab is parsing the nlist records in the binary. Only a tiny
subset of those nlist records are "stabs". Most are just the format by which
MachO expresses its symbol table. So all that needs to be t
On 30/07/2019 11:53, Raphael “Teemperor” Isemann wrote:
Is the plan for LLDB to just adapt the code that is trying to follow the new
code style or also the code using the LLDB code style?
I don't think there's a "plan" at this moment, but I believe Chris meant
all of LLDB.
I’m in general
Is the plan for LLDB to just adapt the code that is trying to follow the new
code style or also the code using the LLDB code style?
I’m in general in favor of moving LLDB to the LLVM code style because it makes
the LLDB code that interfaces with Clang/LLVM less awkward to write (e.g. no
more co
On Mon, 2019-07-29 at 16:32 +0200, Hans Wennborg via Release-testers
wrote:
> Hi everyone,
>
> 9.0.0-rc1 was just tagged from the release_90 branch at r367217
> (tagged as llvmorg-9.0.0-rc1 in the Git monorepo).
>
> Source code and docs are available at https://prereleases.llvm.org/9.0.0/#rc1
>
