Hi Greg,
It turns out that the problem I was having was fixed when I patched a
bug in DwarfSymbolFile:
http://reviews.llvm.org/D14538
But thanks for the additional info.
Aidan
On 12/11/2015 17:54, Greg Clayton wrote:
On Nov 5, 2015, at 9:43 AM, Aidan Dodds via lldb-dev
wrote:
I believe
Hi all,
I'd like to do a few things with our swig generation and handling:
* Create a maintainer-mode style setup where the swig Python bindings are
generated and checked into the repo (I'll call it the static python
binding).
This will be used by default, removing the need for most people and a
On Fri, Nov 13, 2015 at 9:02 AM Todd Fiala via lldb-dev <
lldb-dev@lists.llvm.org> wrote:
> Hi all,
>
> I'd like to do a few things with our swig generation and handling:
>
> * Create a maintainer-mode style setup where the swig Python bindings are
> generated and checked into the repo (I'll call
On Fri, Nov 13, 2015 at 9:43 AM, Zachary Turner wrote:
> On Fri, Nov 13, 2015 at 9:02 AM Todd Fiala via lldb-dev <
> lldb-dev@lists.llvm.org> wrote:
>
>> Hi all,
>>
>> I'd like to do a few things with our swig generation and handling:
>>
>> * Create a maintainer-mode style setup where the swig Py
On Fri, Nov 13, 2015 at 10:24 AM, Todd Fiala wrote:
>
>
> On Fri, Nov 13, 2015 at 9:43 AM, Zachary Turner
> wrote:
>
>> On Fri, Nov 13, 2015 at 9:02 AM Todd Fiala via lldb-dev <
>> lldb-dev@lists.llvm.org> wrote:
>>
>>> Hi all,
>>>
>>> I'd like to do a few things with our swig generation and han
I will probably tackle this as two phases:
Phase 1:
* Python script modernization (the python swig wrapper generation)
* Move Xcode onto it.
Phase 2:
* The maintainer-mode, static Python binding generation changes for cmake
and Xcode.
I want to make sure we have proven, still-functional Python f
Looks like everything was covered. Thanks, all!
On Thu, Nov 12, 2015 at 7:07 PM, Zachary Turner wrote:
> Thanks! I actually forgot, there's one more file for the lldb-gtest
> target. It's PythonExceptionStateTests.cpp.
>
> Thanks for the help
>
> On Thu, Nov 12, 2015 at 6:05 PM Jason Molenda
On Fri, Nov 13, 2015 at 10:24 AM Todd Fiala wrote:
> On Fri, Nov 13, 2015 at 9:43 AM, Zachary Turner
> wrote:
>
>> On Fri, Nov 13, 2015 at 9:02 AM Todd Fiala via lldb-dev <
>> lldb-dev@lists.llvm.org> wrote:
>>
>>> Hi all,
>>>
>>> I'd like to do a few things with our swig generation and handling
Hi,
I am running on Ubuntu Linux. I am using a custom debugger built upon LLDB C++
API using version 3.7.
The target program issues a lot of "legitimate" SIGSEGV signals that it handles
itself. Its signal handler runs on a separate stack (it uses sigaltstack() and
SA_ONSTACK). Now, sometimes a b
Currently you can't disassemble a section, nor would you probably want to since
there are padding bytes in between functions.
The easiest way is to get all SBSymbol objects and ask each one for the
instructions if they are code:
(lldb) script
Python Interactive Interpreter. To exit, type 'quit(
On 13/11/15 19:31, Greg Clayton wrote:
Currently you can't disassemble a section, nor would you probably want to since
there are padding bytes in between functions.
The easiest way is to get all SBSymbol objects and ask each one for the
instructions if they are code:
(lldb) script
Python In
Nice one ,
Cheers mate
On 13/11/15 23:30, kwadwo amankwa wrote:
Nice one ,
Cheers mate
On 13/11/15 19:31, Greg Clayton wrote:
Currently you can't disassemble a section, nor would you probably
want to since there are padding bytes in between functions.
The easiest way is to get all SBSymbol
12 matches
Mail list logo
