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: [email protected] > Date: Mon, 12 Oct 2015 13:25:45 +0100 > Subject: Re: [lldb-dev] Thread resumes with stale signal after executing > InferiorCallMmap > To: [email protected] > CC: [email protected]; [email protected] > > On 8 October 2015 at 17:08, Eugene Birukov <[email protected]> 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
_______________________________________________ lldb-dev mailing list [email protected] http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
