<div class="gmail_extra"><div class="gmail_quote">On Mon, Dec 10, 2012 at 12:35 PM, Mark Atkinson <span dir="ltr"><<a href="mailto:atkin901@gmail.com" target="_blank">atkin901@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
vex x86->IR: unhandled instruction bytes: 0xF 0xB 0x90 0x90<br>
==33074== valgrind: Unrecognised instruction at address 0x380434e9.<br>
==33074==    at 0x380434E9: ??? (in<br>
/usr/local/lib/valgrind/memcheck-x86-freebsd)<br>
==33074==    by 0x323C48: qt_safe_select(int, fd_set*, fd_set*,<br>
fd_set*, timeval const*) (qcore_unix.cpp:83)<br>
==33074==    by 0x2803B1: select_msecs(int, fd_set*, fd_set*, int)<br>
(qprocess_unix.cpp:998)<br>
==33074==    by 0x28021D: QProcessPrivate::waitForStarted(int)<br>
(qprocess_unix.cpp:1031)<br>
==33074==    by 0x1FFA02: QProcess::waitForStarted(int)<br>
(qprocess.cpp:1687)<br>
==33074==    by 0x1FEAEA: QProcess::waitForFinished(int)<br>
(qprocess.cpp:1752)<br>
==33074==    by 0x805487A: AutoMoc::echoColor(QString const&)<br>
(kde4automoc.cpp:74)<br>
==33074==    by 0x805264F: AutoMoc::generateMoc(QString const&,<br>
QString const&) (kde4automoc.cpp:569)<br>
==33074==    by 0x804F13A: AutoMoc::run() (kde4automoc.cpp:470)<br>
==33074==    by 0x804AAEE: main (kde4automoc.cpp:114)<br>
<br>
Full valgrind output is at <a href="http://pastebin.com/KQTKYGX5" target="_blank">http://pastebin.com/KQTKYGX5</a><br>
</blockquote><div><br>This sounds like a valgrind bug I reported related to sigreturn:<br><br><a href="https://bitbucket.org/stass/valgrind-freebsd/issue/4/crash-in-x86_freebsd_subst_for_sigreturn">https://bitbucket.org/stass/valgrind-freebsd/issue/4/crash-in-x86_freebsd_subst_for_sigreturn</a><br>
<br>Unfortunately I don't understand the mechanics of signal handling well enough to take this to completion.<br></div></div></div>