* Peter Maydell (peter.mayd...@linaro.org) wrote: > On 25 April 2017 at 11:41, Dr. David Alan Gilbert (git) > <dgilb...@redhat.com> wrote: > > From: "Dr. David Alan Gilbert" <dgilb...@redhat.com> > > > > The following changes since commit f4b5b021c847669b1c78050aea26fe9abceef6dd: > > > > Merge remote-tracking branch 'remotes/cody/tags/block-pull-request' into > > staging (2017-04-25 09:21:54 +0100) > > > > are available in the git repository at: > > > > git://github.com/dagrh/qemu.git tags/pull-hmp-20170425 > > > > for you to fetch changes up to 1eb8e78dd1cd4e0b4170fd42f6d8882c867f334b: > > > > tests: Add a tester for HMP commands (2017-04-25 11:26:52 +0100) > > > > ---------------------------------------------------------------- > > HMP pull with fixed test/strcmp case > > > > ---------------------------------------------------------------- > > test-hmp fails for me on OSX hosts: > > TEST: tests/test-hmp... (pid=6008) > /aarch64/hmp/n810: > qemu: qemu_mutex_lock: Invalid argument > Broken pipe > FAIL > GTester: last random seed: R02Sd714920da46f8a0e37afec762c6ee23b > (pid=6013) > /aarch64/hmp/tosa: > qemu: qemu_mutex_lock: Invalid argument > Broken pipe > FAIL > GTester: last random seed: R02Sf3025925b9db75bdfdd9f09cf3119ad5 > etc etc. > > Can't do a backtrace, I'm afraid -- Apple's debugger doesn't seem > to work if you're not root and the lack of X11 forwarding on the > box I'm using remotely interacts really badly with qtest's > desire to run qemu as a background process that it's hard to > attach a debugger to. Something's probably not initializing > a mutex, though -- Linux by default treats zeroes as a valid > initialized mutex so it won't notice. You may be able to repro > on Linux by using the Linux PTHREAD_MUTEX_ERRORCHECK_NP > mutex attr, possibly.
Hmm, does running with QTEST_LOG=1 get you any more detail? Dave > thanks > -- PMM -- Dr. David Alan Gilbert / dgilb...@redhat.com / Manchester, UK
