Re: [lldb-dev] Identifying instructions that definitely access memory

2019-11-12 Thread Vangelis Tsiatsianas via lldb-dev
3 PM > To: via lldb-dev > Cc: Vangelis Tsiatsianas > Subject: Re: [lldb-dev] Identifying instructions that definitely access memory > > Hello, > > I decided to try once more with a follow-up email, since my previous one got > no responses (I hope it’s not considered

Re: [lldb-dev] Identifying instructions that definitely access memory

2019-11-07 Thread Tatyana Krasnukha via lldb-dev
Of Vangelis Tsiatsianas via lldb-dev Sent: Tuesday, November 5, 2019 3:43 PM To: via lldb-dev Cc: Vangelis Tsiatsianas Subject: Re: [lldb-dev] Identifying instructions that definitely access memory Hello, I decided to try once more with a follow-up email, since my previous one got no responses (I hope

Re: [lldb-dev] Identifying instructions that definitely access memory

2019-11-05 Thread Vangelis Tsiatsianas via lldb-dev
Hello, I decided to try once more with a follow-up email, since my previous one got no responses (I hope it’s not considered rude to send more than one message in a row for a particular question). To sum up and clarify my previous question, what I need is a way to track memory stores and save

[lldb-dev] Identifying instructions that definitely access memory

2019-10-20 Thread Vangelis Tsiatsianas via lldb-dev
Hello, I am looking for a way to identify loads, stores and any other kind of instruction that definitely perform memory access and extract the address operand(s), however I was not able to find a cross-architecture API. The closest I stumbled upon are "MCInstrDesc::mayLoad()" and