The usual thing to do in this case is to look in the CODE_OWNERS file and see
who is responsible for the area you're changing, and subscribing them to the
change request.
Jim
> On Aug 16, 2017, at 1:49 PM, Christopher Book via lldb-dev
> wrote:
>
> Hi,
>
> I posted a patch last week for a
Hi,
I posted a patch last week for a crash in gdb-remote I was seeing when
debugging a specific binary.
https://reviews.llvm.org/D36620
Is there someone that I should add to review it?
Thanks,
Chris Book
___
lldb-dev mailing list
lldb-dev@lists.llvm.o
I would look at existing code and mimic what other NativeRegisterContextLinux
classes do, but the basics are:
1 - you define register information for each register (ID (register index that
starts at zero and increases with no gaps), name, alt name, offset, size, type)
so that all registers have
Hi,
I am new to the lldb development and trying to add support for ppc64le.
Now, I am having some problems to handle the breakpoints.
In the file /lldb/source/Plugins/Process/gdb-remote/ProcessGDBRemote.cpp:1868,
I am not able to get the PC address.
I created a new file (NativeRegisterContextLi
All green in Debian:
https://buildd.debian.org/status/package.php?p=llvm-toolchain-5.0
Except that I had to force the usage of gcc 6 instead gcc 7 because of
https://bugs.llvm.org/show_bug.cgi?id=34140
(other versions are also affected)
S
Le 11/08/2017 à 04:00, Hans Wennborg via Release-test
