Re: [lldb-dev] [Bug 25896] New: Hide stack frames from specific source files

[Tamas Berghammer via lldb-dev]

We are not working on this feature for android at the moment and if we ever
implement it we will most likely do it in the UI side (inside Android
Studio) the same way Jason described in
https://llvm.org/bugs/show_bug.cgi?id=25896#c1

On Sun, Dec 20, 2015 at 9:01 PM Todd Fiala via lldb-dev <
lldb-dev@lists.llvm.org> wrote:

> Sounds like you almost want the ability to do a backtrace projection.  At
> one point I wanted this for cross C++/Java frames, but I haven't worked on
> that problem in some time.
>
> Android folks - did we ever add anything to support hiding some of the
> trampolines or other call sites involved in the C++/Java transitions?
>
> -Todd
>
> On Sat, Dec 19, 2015 at 3:44 PM, via lldb-dev 
> wrote:
>
>> Bug ID 25896  Summary Hide
>> stack frames from specific source files Product lldb Version unspecified
>> Hardware All OS All Status NEW Severity enhancement Priority P Component All
>> Bugs Assignee lldb-dev@lists.llvm.org Reporter chinmayga...@gmail.com CC
>> llvm-b...@lists.llvm.org Classification Unclassified
>>
>> When my program is paused in the debugger, I would like to hide stack frames
>> originating from certain source files (or libraries) from appearing in the
>> backtrace. These frames usually correspond to standard library functions 
>> that I
>> am not in the process of actively debugging.
>>
>> On a similar note, I did find `target.process.thread.step-avoid-regexp` which
>> allows me to avoid stepping into select frames. However, I want to also
>> suppress these frames in the backtrace listing, and, avoid showing the same
>> when move up and down the bracktrace.
>>
>> --
>> You are receiving this mail because:
>>
>>- You are the assignee for the bug.
>>
>>
>> ___
>> lldb-dev mailing list
>> lldb-dev@lists.llvm.org
>> http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
>>
>>
>
>
> --
> -Todd
> ___
> 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] [Bug 25896] New: Hide stack frames from specific source files

[Todd Fiala via lldb-dev]

Okay, thanks Tamas!

On Mon, Dec 21, 2015 at 3:20 AM, Tamas Berghammer 
wrote:

> We are not working on this feature for android at the moment and if we
> ever implement it we will most likely do it in the UI side (inside Android
> Studio) the same way Jason described in
> https://llvm.org/bugs/show_bug.cgi?id=25896#c1
>
> On Sun, Dec 20, 2015 at 9:01 PM Todd Fiala via lldb-dev <
> lldb-dev@lists.llvm.org> wrote:
>
>> Sounds like you almost want the ability to do a backtrace projection.  At
>> one point I wanted this for cross C++/Java frames, but I haven't worked on
>> that problem in some time.
>>
>> Android folks - did we ever add anything to support hiding some of the
>> trampolines or other call sites involved in the C++/Java transitions?
>>
>> -Todd
>>
>> On Sat, Dec 19, 2015 at 3:44 PM, via lldb-dev 
>> wrote:
>>
>>> Bug ID 25896  Summary Hide
>>> stack frames from specific source files Product lldb Version unspecified
>>> Hardware All OS All Status NEW Severity enhancement Priority P Component All
>>> Bugs Assignee lldb-dev@lists.llvm.org Reporter chinmayga...@gmail.com CC
>>> llvm-b...@lists.llvm.org Classification Unclassified
>>>
>>> When my program is paused in the debugger, I would like to hide stack frames
>>> originating from certain source files (or libraries) from appearing in the
>>> backtrace. These frames usually correspond to standard library functions 
>>> that I
>>> am not in the process of actively debugging.
>>>
>>> On a similar note, I did find `target.process.thread.step-avoid-regexp` 
>>> which
>>> allows me to avoid stepping into select frames. However, I want to also
>>> suppress these frames in the backtrace listing, and, avoid showing the same
>>> when move up and down the bracktrace.
>>>
>>> --
>>> You are receiving this mail because:
>>>
>>>- You are the assignee for the bug.
>>>
>>>
>>> ___
>>> lldb-dev mailing list
>>> lldb-dev@lists.llvm.org
>>> http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
>>>
>>>
>>
>>
>> --
>> -Todd
>> ___
>> lldb-dev mailing list
>> lldb-dev@lists.llvm.org
>> http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
>>
>


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

Re: [lldb-dev] lldb -c corefile get segmentation fault on centos7

[Greg Clayton via lldb-dev]

Something is probably NULL, like maybe the register context from frame 1 or 
frame 2. Make this crash again and then switch to each frame and dump all of 
the local variables. 
> On Dec 20, 2015, at 9:30 PM, 陶征霖 via lldb-dev  wrote:
> 
> Hi,
> 
> I build llvm+clang+lldb 3.7 successfully on centos7, and lldb -p PID works 
> pretty well. However when I tried lldb -c corefile executable_bin, lldb 
> itself core dumpped. Attached the following core info which is debugged by 
> gdb:
> [root@dn-cn-controller-4fbd4 data1]# lldb -c a.corefile 
> /usr/local/myproject/bin/cnode
> (lldb) target create "/usr/local/myproject/bin/cnode" --core "a.corefile"
> Segmentation fault (core dumped)
> 
> And then I tried gdb to check the lldb call stack:
> (gdb) info threads
>   Id   Target Id Frame
>   3Thread 0x7f81c4795700 (LWP 64) 0x7f81c9ed46d5 in 
> pthread_cond_wait@@GLIBC_2.3.2 ()
>from /lib64/libpthread.so.0
>   2Thread 0x7f81ce580740 (LWP 59) 0x7f81c9ed46d5 in 
> pthread_cond_wait@@GLIBC_2.3.2 ()
>from /lib64/libpthread.so.0
> * 1Thread 0x7f81c3f94700 (LWP 65) 0x7f81cbe00630 in 
> lldb_private::ArchSpec::GetMachine() const ()
>from /opt/dependency/tools/bin/../lib64/liblldb.so.3.7
> (gdb) bt
> #0  0x7f81cbe00630 in lldb_private::ArchSpec::GetMachine() const ()
>from /opt/dependency/tools/bin/../lib64/liblldb.so.3.7
> #1  0x7f81cc20458f in 
> RegisterContextPOSIX_x86::RegisterContextPOSIX_x86(lldb_private::Thread&, 
> unsigned int, lldb_private::RegisterInfoInterface*) () from 
> /opt/dependency/tools/bin/../lib64/liblldb.so.3.7
> #2  0x7f81cc153a24 in 
> RegisterContextCorePOSIX_x86_64::RegisterContextCorePOSIX_x86_64(lldb_private::Thread&,
>  lldb_private::RegisterInfoInterface*, lldb_private::DataExtractor const&, 
> lldb_private::DataExtractor const&) ()
>from /opt/dependency/tools/bin/../lib64/liblldb.so.3.7
> #3  0x7f81cc151e5e in 
> ThreadElfCore::CreateRegisterContextForFrame(lldb_private::StackFrame*) ()
>from /opt/dependency/tools/bin/../lib64/liblldb.so.3.7
> #4  0x7f81cc1523b3 in ThreadElfCore::GetRegisterContext() ()
>from /opt/dependency/tools/bin/../lib64/liblldb.so.3.7
> #5  0x7f81cbfae9e2 in 
> lldb_private::StackFrameList::GetFramesUpTo(unsigned int) ()
>from /opt/dependency/tools/bin/../lib64/liblldb.so.3.7
> #6  0x7f81cbfaf3e7 in 
> lldb_private::StackFrameList::ResetCurrentInlinedDepth() ()
>from /opt/dependency/tools/bin/../lib64/liblldb.so.3.7
> #7  0x7f81cbfd32e2 in 
> lldb_private::Thread::ShouldStop(lldb_private::Event*) ()
>from /opt/dependency/tools/bin/../lib64/liblldb.so.3.7
> #8  0x7f81cbfd98d2 in 
> lldb_private::ThreadList::ShouldStop(lldb_private::Event*) ()
>from /opt/dependency/tools/bin/../lib64/liblldb.so.3.7
> #9  0x7f81cbf997bb in 
> lldb_private::Process::ShouldBroadcastEvent(lldb_private::Event*) ()
>from /opt/dependency/tools/bin/../lib64/liblldb.so.3.7
> #10 0x7f81cbf998a1 in 
> lldb_private::Process::HandlePrivateEvent(std::shared_ptr&)
>  ()
>from /opt/dependency/tools/bin/../lib64/liblldb.so.3.7
> #11 0x7f81cbf9a77a in lldb_private::Process::RunPrivateStateThread(bool) 
> ()
>from /opt/dependency/tools/bin/../lib64/liblldb.so.3.7
> #12 0x7f81cbdf7db2 in 
> lldb_private::HostNativeThreadBase::ThreadCreateTrampoline(void*) ()
>from /opt/dependency/tools/bin/../lib64/liblldb.so.3.7
> #13 0x7f81c9ed0dc5 in start_thread () from /lib64/libpthread.so.0
> #14 0x7f81c91c821d in clone () from /lib64/libc.so.6
> 
> Any suggesstion about why lldb -c core dump?
> 
> Thanks,
> Zhenglin
> ___
> 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

[lldb-dev] Fwd: Enrico abroad for 2 weeks

[Enrico Granata via lldb-dev]

Sending again to right audience since I suspect most LLVM folks don’t really 
care :-)

> Begin forwarded message:
> 
> From: Enrico Granata 
> Subject: Enrico abroad for 2 weeks
> Date: December 21, 2015 at 3:29:51 PM PST
> To: llvm-...@lists.llvm.org
> 
> Hi,
> some of you may know this already - but anyway here goes
> 
> I am going to be abroad for 2 weeks starting tomorrow - away from keyboard 
> and with very restricted network access
> As such, I will take longer than usual to review patches and respond to 
> concerns
> 
> I will be back to the United States on January 6 2016.
> 
> Till then, happy holiday season to everyone!
> 
> - Enrico
> 📩 egranata@.com ☎️ 27683
> 


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