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
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
On 31/10/2019 20:51, Jim Ingham via lldb-dev wrote:
It looks like this change is causing problems with swift. I was talking a
little bit with Davide about this and it seems like it wasn't obvious how this
was designed to work. So here's what this was intended to do (apologies if
this is at t
On Mon, 04 Nov 2019 16:16:30 +0100, Konrad Kleine via lldb-dev wrote:
> 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
Sorry, my brain is not working this morning, I answered your question in the
review comments…
Jim
> On Nov 4, 2019, at 7:28 AM, Pavel Labath wrote:
>
> On 31/10/2019 20:51, Jim Ingham via lldb-dev wrote:
>> It looks like this change is causing problems with swift. I was talking a
>> little
On 04/11/2019 18:19, Jim Ingham wrote:
Sorry, my brain is not working this morning, I answered your question in the
review comments…
Jim
NP, maybe let's continue the discussion there? I find it useful to have
the actual code change around..
___
l
