Hi guys,
I've seen that recently the test
lldb-Suite.macosx/queues.TestQueues.py fails non-deterministically.
E.g.
http://green.lab.llvm.org/green/view/LLDB/job/lldb-cmake/21271/testReport/
http://green.lab.llvm.org/green/view/LLDB/job/lldb-cmake/21244/testReport/
http://green.lab.llvm.org/green/
On Thu, Mar 7, 2019 at 7:04 AM Gábor Márton via lldb-dev
wrote:
>
> Hi guys,
>
> I've seen that recently the test
> lldb-Suite.macosx/queues.TestQueues.py fails non-deterministically.
>
> E.g.
> http://green.lab.llvm.org/green/view/LLDB/job/lldb-cmake/21271/testReport/
> http://green.lab.llvm.org/
https://bugs.llvm.org/show_bug.cgi?id=40609
Frank Praznik changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Resolution|---
> On Mar 7, 2019, at 7:43 AM, Davide Italiano wrote:
>
> On Thu, Mar 7, 2019 at 7:04 AM Gábor Márton via lldb-dev
> mailto:lldb-dev@lists.llvm.org>> wrote:
>>
>> Hi guys,
>>
>> I've seen that recently the test
>> lldb-Suite.macosx/queues.TestQueues.py fails non-deterministically.
>>
>> E.g.
Hi Ben,
I think I already answered this last week:
http://lists.llvm.org/pipermail/lldb-dev/2019-February/014789.html
I don't think you'll get an answer here without posting the
problematic source or giving any more information as I described in my
mail.
Cheers,
- Raphael
Am Do., 7. März 2019 u
Hey Raphael,
Yes, you did advise me to drop a D->dumpColor() call in to
getASTRecordLayout(). For frustrating reasons I still haven't been able to
capture those logs but when I do I will report back.
Thanks so much for your help and quick response!
Ben
On Thu, Mar 7, 2019 at 12:56 PM Raphael I
Ah I see what happened. My original e-mail was delayed because it was too
large but it was recently accepted by a moderator.
On Thu, Mar 7, 2019 at 1:19 PM Ben Ruthig wrote:
> Hey Raphael,
>
> Yes, you did advise me to drop a D->dumpColor() call in to
> getASTRecordLayout(). For frustrating re
We have a build option to build LLDB without Python. This option is
automatically set if Cmake can't find or "validate" your Python
distribution.
Since LLDB is rarely built with this option, nobody discovers when this
configuration breaks. For example, if you try it today, you'll get a
handful o
Even though you can just use debugserver/lldb-server and debug remotely, many
people find it handy to be able to run a debugger directly on the device they
are using. But requiring that you port Python and bundle it with your embedded
platform just to get a debugger there is a pretty big ask.
I'm in favor of this. FWIW, I will be surprised if lldb works at all
with that option.
On Thu, Mar 7, 2019 at 10:28 AM Adrian McCarthy via lldb-dev
wrote:
>
> We have a build option to build LLDB without Python. This option is
> automatically set if Cmake can't find or "validate" your Python di
On 07/03/2019 19:27, Adrian McCarthy via lldb-dev wrote:
We have a build option to build LLDB without Python. This option is
automatically set if Cmake can't find or "validate" your Python
distribution.
Since LLDB is rarely built with this option, nobody discovers when this
configuration bre
On Thu, Mar 7, 2019 at 11:03 AM Jim Ingham via lldb-dev <
lldb-dev@lists.llvm.org> wrote:
> Even though you can just use debugserver/lldb-server and debug remotely,
> many people find it handy to be able to run a debugger directly on the
> device they are using. But requiring that you port Python
On 07/03/2019 20:29, Davide Italiano via lldb-dev wrote:
I'm in favor of this. FWIW, I will be surprised if lldb works at all
with that option.
I would actually be also surprised if it works. However, the option I
think is important to keep is to be able to build lldb-server without
python a
Does lldb-server for Android currently use this flag? I was under the
impression it just linked against Python anyway.
On Thu, Mar 7, 2019 at 11:50 AM Pavel Labath via lldb-dev <
lldb-dev@lists.llvm.org> wrote:
> On 07/03/2019 20:29, Davide Italiano via lldb-dev wrote:
> > I'm in favor of this.
I second this opinion and have really not much further to add, except
maybe that just yesterday to my delight I actually discovered this
option and now promptly use it as the default when building my debugger
variant. It removed a lot of python warnings when running my handbuilt
lldb on macos.
On 07/03/2019 20:52, Zachary Turner wrote:
Does lldb-server for Android currently use this flag? I was under the
impression it just linked against Python anyway.
No, it doesn't link against python. In fact, when targetting android, we
default to disabling all external dependencies. LLDBConfig
> On Mar 7, 2019, at 11:37 AM, Zachary Turner wrote:
>
>
>
> On Thu, Mar 7, 2019 at 11:03 AM Jim Ingham via lldb-dev
> wrote:
> Even though you can just use debugserver/lldb-server and debug remotely, many
> people find it handy to be able to run a debugger directly on the device they
> a
Yes, Pavel pointed out one specific case where it is used, and that case
definitely needs to be supported.
We've talked in the past about fixing the layering in such a way that all
Python related code is in ScriptInterpreterPython, but there's definitely a
non-trivial amount of work needed to make
OK, thanks all for the discussion.
I'll try to fix the immediate problems (the build breakage and the Python
detection). If I get more ambitious, I'll make another proposal.
On Thu, Mar 7, 2019 at 12:55 PM Zachary Turner wrote:
> Yes, Pavel pointed out one specific case where it is used, and t
You can also dump() the AST to a file on disk if that is easier to
capture than stderr. See the overload of `dump()` that takes a stream:
https://clang.llvm.org/doxygen/ASTDumper_8cpp_source.html#l00225
- Raphael
Am Do., 7. März 2019 um 19:20 Uhr schrieb Ben Ruthig :
>
> Hey Raphael,
>
> Yes, you
20 matches
Mail list logo
