I'd be very interested in using lldb in my regular workflow but, I'm
currently using cgdb because its single key mode is ready convenient for
common operations:
f - finish
s - step
n - next
d - down
u - up
```
rr record $exe $args
rr replay -d cgdb
# happy debugging
# rm -r ~/.local/share/rr
Sounds good to me :-)
On Fri, Aug 30, 2019 at 1:27 PM Davide Italiano via lldb-dev
wrote:
>
> On Fri, Aug 30, 2019 at 1:44 AM Raphael “Teemperor” Isemann via
> lldb-dev wrote:
> >
> > Hi all,
> >
> > I have to admit I’m getting a bit confused lately where to put tests.
> > Especially for testin
On Fri, Aug 30, 2019 at 1:44 AM Raphael “Teemperor” Isemann via
lldb-dev wrote:
>
> Hi all,
>
> I have to admit I’m getting a bit confused lately where to put tests.
> Especially for testing LLDB commands it’s not obvious where to put files as
> we test some commands directly in the top-level te
Hi,
I've created a text file[1] in the SVN repository that developers can
update in order to request commit access to the GitHub repository.
All you need to do is add a line in the form of
$SVN_USERNAME:$GITHUB_USERNAME
Please add your information to this file before SVN becomes readonly
on Oct
Hello everyone,
9.0.0-rc3 was tagged today from the release_90 branch at r370450. In
the Git monorepo, it's tagged as llvmorg-9.0.0-rc3.
Source code and docs are available at https://prereleases.llvm.org/9.0.0/#rc3
Binaries will be added as they become available.
There are currently no open rel
I agree - I wouldn't expect class AA to be a match for "A::".
> -Original Message-
> From: lldb-dev On Behalf Of Pavel Labath
> via lldb-dev
> Sent: Friday, August 30, 2019 1:28 AM
> To: Jim Ingham ; LLDB
> Subject: [EXT] Re: [lldb-dev] Breakpoint matching with -n seems to have
> gotten
Raphael, this sounds like a good idea.
Am Fr., 30. Aug. 2019 um 10:44 Uhr schrieb Raphael “Teemperor” Isemann via
lldb-dev :
> Hi all,
>
> I have to admit I’m getting a bit confused lately where to put tests.
> Especially for testing LLDB commands it’s not obvious where to put files as
> we test
Hi all,
I have to admit I’m getting a bit confused lately where to put tests.
Especially for testing LLDB commands it’s not obvious where to put files as we
test some commands directly in the top-level test folder (e.g. quit, help,
settings), some are in /functionalities with a _command suffix
