[Lldb-commits] [PATCH] D74398: [lldb-server] jThreadsInfo returns stack memory

[Jason Molenda via lldb-commits]

> On Mar 21, 2020, at 10:25 PM, Jason Molenda via Phabricator via lldb-commits <lldb-commits at lists.llvm.org> wrote:
> 

> 
>  0x100001232 <+18>: movq   %rax, -0x68(%rbp)
>  0x100001236 <+22>: callq  0x100001350               ; std::__1::vector<unsigned long long, std::__1::allocator<unsigned long long> >::vector at vector:497
>  0x10000123b <+27>: movabsq $0x100000000, %rax        ; imm = 0x100000000 
> 
> 

> <   5> send packet: $c#63
> < 624> read packet: $T05thread:5ada71;threads:5ada71;thread-pcs:10000123b;00:58fabfeffe7f0000;01:0000000000000000;02:80fbbfeffe7f0000;03:90fabfeffe7f0000;04:58fabfeffe7f0000;05:58fabfeffe7f0000;06:60fabfeffe7f0000;07:e0f9bfeffe7f0000;08:0000000000000000;09:0000000000000000;0a:0000000000000000;0b:0000000000000000;0c:0000000000000000;0d:0000000000000000;0e:0000000000000000;0f:0000000000000000;10:3b12000001000000;11:0202000000000000;12:2b00000000000000;13:0000000000000000;14:0000000000000000;metype:6;mecount:2;medata:2;medata:0;memory:0x7ffeefbffa60=70fabfeffe7f0000fdd7f765ff7f0000;memory:0x7ffeefbffa70=00000000000000000100000000000000;#00
> <  18> send packet: $z0,10000123b,1#1c
> <   6> read packet: $OK#00
> <  18> send packet: $vCont;s:5ada71#b5
> < 624> read packet: $T05thread:5ada71;threads:5ada71;thread-pcs:100001245;00:0000000001000000;01:0000000000000000;02:80fbbfeffe7f0000;03:90fabfeffe7f0000;04:58fabfeffe7f0000;05:58fabfeffe7f0000;06:60fabfeffe7f0000;07:e0f9bfeffe7f0000;08:0000000000000000;09:0000000000000000;0a:0000000000000000;0b:0000000000000000;0c:0000000000000000;0d:0000000000000000;0e:0000000000000000;0f:0000000000000000;10:4512000001000000;11:0202000000000000;12:2b00000000000000;13:0000000000000000;14:0000000000000000;metype:6;mecount:2;medata:1;medata:0;memory:0x7ffeefbffa60=70fabfeffe7f0000fdd7f765ff7f0000;memory:0x7ffeefbffa70=00000000000000000100000000000000;#00



(and anyone reading this packet sequence closely might ask, Hey, why doesn't lldb set the breakpoint on the next branch instruction/end-of-address-range after the return address, instead of the return address?  It would save a whole private stop!  This person would be correct and it would be interesting to look into finding a way to make the return thread plan do this! :)