Oh well, you win some, you lose some :) I was expecting that to be the
case. At least i don't have to go down that rabbit hole with this info in
hand.
Thanks!
Mario
On Jan 7, 2015 12:19 AM, "Greg Clayton" wrote:
>
> > On Jan 6, 2015, at 2:58 PM, Mario Zechner
> wrote:
> >
> > This is excellent
> On Jan 6, 2015, at 2:58 PM, Mario Zechner wrote:
>
> This is excellent news. I assume your refer to the Python script i posted in
> [1]. That was a port of our production code to illustrate issues with high
> frequency process suspends/resumes in conjunction with tracing
> steps/breakpoints
This is excellent news. I assume your refer to the Python script i posted
in [1]. That was a port of our production code to illustrate issues with
high frequency process suspends/resumes in conjunction with tracing
steps/breakpoints.
If reading from the inferiors memory while the process is runnin
It is fine to not require that a process be stopped in order to read memory.
Are you still doing your python based approach? We are currently enforcing that
a process must be stopped in order to read memory in SBProcess::ReadMemory()
where we acquire the run lock and make sure the process stays
