> FWIW this mail did not arrive as reply to any previous post on the list
> so it may not be obvious for reviewers what "this one" refers to. You
> may want to check what went wrong (also it arrived as HTML so that
> quotes below are broken).
Ok, sorry, gmail backend does nasty things. I should mi
ping
My first two submissions were quite broken, but I think that this one was
solid enough. Though there was too much silence. Do I repatch for the
current head? Something worth changing? Or it is not worth patching it?
(IMHO it should be patched at some time).
On Mon, Nov 19, 2012 at 8:01 PM, A
ping
On Sat, Oct 20, 2012 at 4:15 PM, Alex Barcelo wrote:
> qemu-user needs SIGSEGV (at least) for some internal use. If the guest
> application masks it and does unsafe sigprocmask, then the application
> crashes. Problems happen in applications with self-modifying code (who
> also change the
qemu-user needs SIGSEGV (at least) for some internal use. If the guest
application masks it and does unsafe sigprocmask, then the application
crashes. Problems happen in applications with self-modifying code (who
also change the signal mask). Other guest applications may have related
problems if th
