Re: [lldb-dev] [llvm-dev] RFC: Using GitHub Actions for CI testing on the release/* branches

2019-11-11 Thread David Blaikie via lldb-dev
Not having given it deep thought/analysis, nor understanding much of the GIT infrastructure here, but: Sounds good to me, for whatever that's worth :) On Mon, Nov 11, 2019 at 4:32 PM Tom Stellard via llvm-dev < llvm-...@lists.llvm.org> wrote: > Hi, > > I would like to start using GitHub

[lldb-dev] RFC: Using GitHub Actions for CI testing on the release/* branches

2019-11-11 Thread Tom Stellard via lldb-dev
Hi, I would like to start using GitHub Actions[1] for CI testing on the release/* branches. As far as I know we don't have any buildbots listening to the release branches, and I think GitHub Actions are a good way for us to quickly bring-up some CI jobs there. My proposal is to start by adding

Re: [lldb-dev] Setting breakpoint on file and function name doesn't work as expected.

2019-11-11 Thread Konrad Kleine via lldb-dev
Hi Jim, Am Fr., 8. Nov. 2019 um 19:57 Uhr schrieb Jim Ingham : > > > > On Nov 8, 2019, at 1:53 AM, Konrad Kleine wrote: > > > > Jim, > > > > thank you for the explanation. I'm trying to see the situation more from > an end user's perspective. When --file or -f have two different meanings >

[lldb-dev] [Bug 43959] New: 'process signal ...' should probably NOT stop the process

2019-11-11 Thread via lldb-dev
https://bugs.llvm.org/show_bug.cgi?id=43959 Bug ID: 43959 Summary: 'process signal ...' should probably NOT stop the process Product: lldb Version: 9.0 Hardware: PC OS: Linux Status: NEW