[lldb-dev] review for crash patch to gdb remote

[Jim Ingham via lldb-dev]

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 <lldb-dev at lists.llvm.org> wrote:
> 
> 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 at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev