Will do!
> From: lab...@google.com
> Date: Tue, 13 Oct 2015 09:40:28 +0100
> Subject: Re: [lldb-dev] Thread resumes with stale signal after executing
> InferiorCallMmap
> To: eugen...@hotmail.com
> CC: lldb-dev@lists.llvm.org; jing...@apple.com
>
> Sure, fair enough.
al during expression
> evaluation is buggy. Sorry, I am not sure that I will have time to look into
> it deeper - it is not a blocker for me at this time.
>
>> From: lab...@google.com
>> Date: Mon, 12 Oct 2015 13:25:45 +0100
>> Subject: Re: [lldb-dev] Thread resumes with stale s
Re: [lldb-dev] Thread resumes with stale signal after executing
> InferiorCallMmap
> To: eugen...@hotmail.com
> CC: lldb-dev@lists.llvm.org; jing...@apple.com
>
> On 8 October 2015 at 17:08, Eugene Birukov wrote:
> > Yes, that's exactly what I see, thanks a lot!
&g
e
>
> > From: lab...@google.com
> > Date: Thu, 8 Oct 2015 09:13:37 +0100
> > Subject: Re: [lldb-dev] Thread resumes with stale signal after executing
> > InferiorCallMmap
> > To: eugen...@hotmail.com
> > CC: lldb-dev@lists.llvm.org; jing...@apple.com
> >
>
On 8 October 2015 at 17:08, Eugene Birukov wrote:
> Yes, that's exactly what I see, thanks a lot!
You're wellcome.
>
> Does it explain why I see SIGILL reappear when I let process continue after
> mmap execution? I.e. do I need to look into this more?
No. That could still be a bug somewhere. Feel
gt;> broadcaster and is picked up and processed much later.
> >
> > When the expression evaluation completes, the StopInfo from the last
> > "natural" stop should be put back in place in the thread. After all, if
> > you hit a breakpoint, run an expression, t
When the expression evaluation completes, the StopInfo from the last
> "natural" stop should be put back in place in the thread. After all, if you
> hit a breakpoint, run an expression, then ask why that thread stopped, you
> want to see "hit a breakpoint" not "
it a breakpoint" not "ran a function call". Sounds like that is failing
somehow.
Jim
>
> > Subject: Re: [lldb-dev] Thread resumes with stale signal after executing
> > InferiorCallMmap
> > From: jing...@apple.com
> > Date: Wed, 7 Oct 2015 15:08:18 -0700
>
SIG_ILL that is stuck in the broadcaster
and is picked up and processed much later.
> Subject: Re: [lldb-dev] Thread resumes with stale signal after executing
> InferiorCallMmap
> From: jing...@apple.com
> Date: Wed, 7 Oct 2015 15:08:18 -0700
> CC: lldb-dev@lists.llvm.org
> To: eu
Does it only happen for InferiorCallMmap, or does an expression evaluation that
crashes in general set a bad signal on resume? I don't see this behavior in
either case on OS X, so it may be something in the Linux support. Be
interesting to figure out why it behaves this way on Linux, so whatev
Hi,
I am using LLDB 3.7.0 C++ API. My program stops at a certain breakpoint and if
I call SBFrame::EvaluateExpression() there, when I let it go it terminates with
SIG_ILL on an innocent thread. I dug up into this, and there seems to be two
independent problems there, this mail is about the sec
11 matches
Mail list logo
