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

2017-08-16 Thread 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 > wrote: > > Hi, > > I posted a patch last week for a

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

2017-08-16 Thread Christopher Book via lldb-dev
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