On Sun, May 1, 2016 at 2:21 PM, Kamil Rytarowski via lldb-dev <
lldb-dev@lists.llvm.org> wrote:
> It has been noted that LLDB installs its own copy of six.py
> (third_party/Python/module/six/six.py) that conflicts with a standalone
> one lang/py-six (path in pkgsrc).
>
> Could we reuse an external
"p" uses the expression parser and might cause code to be jitted and run in the
program being debugged. If the expression is simple enough, the expression
parser will emulate the IR. With "frame variable", it doesn't use the
expression parser. "frame variable" can display children: "pt.x" or "pt
I am currently working on a language plugin for lldb.
I would like to be able to put a breakpoint on demangled function names, but
even after demangling function names through my custom DWARF parser, lldb won't
autocomplete on demangled names nor break on them.
I though about modifiying the Inde
Hi everyone
There has been previous discussions in this mailing list regarding *E**nabling
Intel(R) Processor Trace collection in LLDB. A new APIs are being developed
to be added to SB APIs that will provide raw traces (collected on
lldb-server side). These APIs are Trace technology independent an
Currently the DWARF provides two things for a mangled function in the
accelerator tables:
1 - the function basename
2 - the full mangled name
So for a C++ function like:
a::b::c(int, float, char)
The accelerator tables would contain "c", and "_ZN1a1b3fooEifc" that would
point the the DWARF fo
On 02.05.2016 18:40, Reid Kleckner wrote:
> On Sun, May 1, 2016 at 2:21 PM, Kamil Rytarowski via lldb-dev
> mailto:lldb-dev@lists.llvm.org>> wrote:
>
> It has been noted that LLDB installs its own copy of six.py
> (third_party/Python/module/six/six.py) that conflicts with a
standalone
>
This may be true, but telling my users "you have to install six" is a
non-starter.
--
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux
Foundation Collaborative Project
> -Original Message-
> From: lldb-dev [mailto:lldb-dev-b
Can we take care of this with python include path ordering? If we are on a
system that has its own six.py somewhere in the python libraries, how is it
picking our version incorrectly? Aren't there search paths for the modules? If
so, we might need to put any compatibility modules into a specific
Having private fallback six.py will work for everybody, just it cannot
be installed into the global path along with Python libraries:
$ pkg_info -L lldb|grep six.py
/usr/pkg/lib/python2.7/site-packages/six.py
Maybe in lldb/utils/?
chieftec$ pkg_info -L lldb|grep py
/usr/pkg/lib/python2.7/site-pa
We'll be at Tied House as usual, starting on Thursday the 5th at 7pm!
If you can, please help us plan and RSVP here: http://meetu.ps/2Wj7Tc
See everyone there!
George
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailma
10 matches
Mail list logo
