[Development] [Q] Good way to handle QEvent::DeferredDelete

Hausmann Simon Simon.Hausmann at digia.com
Mon Dec 30 14:53:07 CET 2013

You can turn off the JIT by setting the QV4_FORCE_INTERPRETER=1 environment variable at runtime.


Fra: Thiago Macieira
Sendt: 12:26 mandag 30. desember 2013
Til: development at qt-project.org
Emne: Re: [Development] [Q] Good way to handle QEvent::DeferredDelete

On segunda-feira, 30 de dezembro de 2013 10:44:15, Elvis Lee wrote:
> #24 0x3b60a0a8 in ?? ()
> #25 0x3b60a0a8 in ?? ()
> Backtrace stopped: previous frame identical to this frame (corrupt stack?)
> I don't know what's here.
> 3b60a000-3b60b000 rwxp 00000000 00:00 0
> 3b60b000-3b60c000 ---p 00000000 00:00 0

It's the JIT'ted code by V8. Nothing except a JIT uses pages simuntaneously
writeable and executable -- they're a major security nightmare.

Unfortunately, I need to know what called it. That's why you need to use 5.2.0
and a debug build. You might need to turn JIT off in V4 too.
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20131230/4a6288bf/attachment.html>

More information about the Development mailing list