Re: [lldb-dev] running lldb-mi with LLDB_DISABLE_PYTHON

[Chunseok Lee via lldb-dev]

Do you have any idea about regression after applying workaround 1 ? (For
example, wrong output in some cases)


2016-09-20 21:37 GMT+09:00 Ilia K :

> Hi!
>
> Please see possible workarounds in https://llvm.org/bugs/show_
> bug.cgi?id=28253.
>
> On Tue, Sep 20, 2016 at 10:57 AM, Chunseok Lee via lldb-dev <
> lldb-dev@lists.llvm.org> wrote:
>
>> Dear lldb dev team,
>>
>> I am working on running lldb-mi on arm32 device(like rpi) for remote
>> debugging usage.
>> Is there any way to run lldb-mi with python disabled ?
>> When building lldb with LLDB_DISABLE_PYTHON, it seems that dataformatter
>> initialization is failed due to the following code in
>> MICmnLLDBDebugger.cpp:59
>>
>> //++
>> //--
>> --
>> // MI summary helper routines
>> static inline bool MI_add_summary(lldb::SBTypeCategory category,
>>   const char *typeName,
>>   lldb::SBTypeSummary::FormatCallback cb,
>>   uint32_t options, bool regex = false) {
>> #if defined(LLDB_DISABLE_PYTHON)
>>   return false;
>> #else
>>   lldb::SBTypeSummary summary =
>>   lldb::SBTypeSummary::CreateWithCallback(cb, options);
>>   return summary.IsValid()
>>  ? category.AddTypeSummary(
>>lldb::SBTypeNameSpecifier(typeName, regex), summary)
>>  : false;
>> #endif
>> }
>>
>> Thank you.
>>
>> BR,
>> Chunseok Lee
>>
>> --
>> Where Do We come from? What Are We? Where Are We Going?
>>
>> ___
>> lldb-dev mailing list
>> lldb-dev@lists.llvm.org
>> http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
>>
>>
>
>
> --
> - Ilia
>



-- 
Where Do We come from? What Are We? Where Are We Going?
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] running lldb-mi with LLDB_DISABLE_PYTHON

[Jim Ingham via lldb-dev]

If you use the MI, that assumes that the server process is the one doing most 
of the work.  lldb is not meant to be a light-weight program, and if you start 
feeding it a lot of symbol information you may find it taking up too many 
resources to really want to run it on your device.   For device debugging, it 
is more efficient to run lldb-server or some other monitor that speaks the 
gdb-remote protocol on the device and then run lldb on the host.  The 
gdb-remote servers can be much more efficient since they don't directly deal 
with debug or symbol information.  We've done a lot of work both for iOS and 
for Android to make lldb's handling of this way of debugging efficient.  The 
changes we made to the gdb-remote protocol to support this work are documented 
in docs/lldb-gdb-remote.txt, though lldb will also run correctly with a vanilla 
gdb-remote server.

Jim

> On Sep 20, 2016, at 12:57 AM, Chunseok Lee via lldb-dev 
>  wrote:
> 
> Dear lldb dev team,
> 
> I am working on running lldb-mi on arm32 device(like rpi) for remote 
> debugging usage.
> Is there any way to run lldb-mi with python disabled ?
> When building lldb with LLDB_DISABLE_PYTHON, it seems that dataformatter 
> initialization is failed due to the following code in 
> MICmnLLDBDebugger.cpp:59   
> 
> //++
> //
> // MI summary helper routines
> static inline bool MI_add_summary(lldb::SBTypeCategory category,
>   const char *typeName,
>   lldb::SBTypeSummary::FormatCallback cb,
>   uint32_t options, bool regex = false) {
> #if defined(LLDB_DISABLE_PYTHON)
>   return false;
> #else
>   lldb::SBTypeSummary summary =
>   lldb::SBTypeSummary::CreateWithCallback(cb, options);
>   return summary.IsValid()
>  ? category.AddTypeSummary(
>lldb::SBTypeNameSpecifier(typeName, regex), summary)
>  : false;
> #endif
> }
> 
> Thank you.
> 
> BR,
> Chunseok Lee
> 
> -- 
> Where Do We come from? What Are We? Where Are We Going?
> ___
> lldb-dev mailing list
> lldb-dev@lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] running lldb-mi with LLDB_DISABLE_PYTHON

[Ilia K via lldb-dev]

Hi!

Please see possible workarounds in
https://llvm.org/bugs/show_bug.cgi?id=28253.

On Tue, Sep 20, 2016 at 10:57 AM, Chunseok Lee via lldb-dev <
lldb-dev@lists.llvm.org> wrote:

> Dear lldb dev team,
>
> I am working on running lldb-mi on arm32 device(like rpi) for remote
> debugging usage.
> Is there any way to run lldb-mi with python disabled ?
> When building lldb with LLDB_DISABLE_PYTHON, it seems that dataformatter
> initialization is failed due to the following code in
> MICmnLLDBDebugger.cpp:59
>
> //++
> //--
> --
> // MI summary helper routines
> static inline bool MI_add_summary(lldb::SBTypeCategory category,
>   const char *typeName,
>   lldb::SBTypeSummary::FormatCallback cb,
>   uint32_t options, bool regex = false) {
> #if defined(LLDB_DISABLE_PYTHON)
>   return false;
> #else
>   lldb::SBTypeSummary summary =
>   lldb::SBTypeSummary::CreateWithCallback(cb, options);
>   return summary.IsValid()
>  ? category.AddTypeSummary(
>lldb::SBTypeNameSpecifier(typeName, regex), summary)
>  : false;
> #endif
> }
>
> Thank you.
>
> BR,
> Chunseok Lee
>
> --
> Where Do We come from? What Are We? Where Are We Going?
>
> ___
> lldb-dev mailing list
> lldb-dev@lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
>
>


-- 
- Ilia
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev