[lldb-dev] Thread resumes with stale signal after executing InferiorCallMmap
Eugene Birukov via lldb-dev
lldb-dev at lists.llvm.org
Tue Oct 13 09:36:12 PDT 2015
> From: labath at google.com
> Date: Tue, 13 Oct 2015 09:40:28 +0100
> Subject: Re: [lldb-dev] Thread resumes with stale signal after executing InferiorCallMmap
> To: eugenebi at hotmail.com
> CC: lldb-dev at lists.llvm.org; jingham at apple.com
> Sure, fair enough.
> If you have made a small repro case already though, it would be great
> if you could file a bug about it, so we don't forget it.
> On 12 October 2015 at 23:23, Eugene Birukov <eugenebi at hotmail.com> wrote:
> > I tried to repro it using standard LLDB client on a simple program that I
> > could share. Well, the problem does not exactly repro as in my case - i.e.
> > the signal is not re-delivered to the thread. But LLDB does get confused
> > state: the program continues but at the same time lldb shows its prompt as
> > if the program were stopped. I.e. the recovery from signal 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: labath at google.com
> >> Date: Mon, 12 Oct 2015 13:25:45 +0100
> >> Subject: Re: [lldb-dev] Thread resumes with stale signal after executing
> >> InferiorCallMmap
> >> To: eugenebi at hotmail.com
> >> CC: lldb-dev at lists.llvm.org; jingham at apple.com
> >> On 8 October 2015 at 17:08, Eugene Birukov <eugenebi at hotmail.com> 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 free to look into it..
> >> pl
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the lldb-dev