I wanted to try importing llvm bugs into a fresh github repo and here's my
result so far (import is still running):
https://github.com/kwk/test-llvm-bz-import-4 . I've written the scripts (
https://github.com/kwk/bz2gh) myself because I wanted to remain in control
and don't make my life more compli
-- Forwarded message -
From: Konrad Kleine
Date: Tue, 21 Apr 2020 at 09:39
Subject: Re: [llvm-dev] RFC: Switching from Bugzilla to Github Issues
[UPDATED]
To: Tom Stellard
Hi Tom.
I haven't read all the replies before mine. Sorry if my idea overlaps with
someone else's.
I have
Hi,
I'm on a machine like this:
Linux #1 SMP Tue Feb 18 16:40:30 EST 2020 ppc64
ppc64 ppc64 GNU/Linux
Red Hat Enterprise Linux Server release 7.8 (Maipo)
It seems that on PPC64 breakpoints are not able to hit, and it doesn't
matter which strategy you choose. Here's an example:
$ sc
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
> depen
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
depending on how they are combined, that's bad IMHO.
>From what I read in your response I get the feeling that you assume a user
knows about the d
I read the LLDB troubleshooting page [1] and found interesting quotes:
> When setting breakpoints in implementation source files (.c, cpp, cxx,
.m, .mm, etc), LLDB by
> default will only search for compile units whose filename matches.
> [...]
> % echo "settings set target.inline-breakpoint-stra
Hello,
I noticed this behavior for LLDB under Linux when setting a breakpoint on a
file and a function name:
When doing "breakpoint set --file --name ", the
is that of the compile unit (CU) and not necessarily where the
function is defined. This is not what an end-user expects.
Take this simpl
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
