I doing the build as part of an Openembedded Bitbake recipe -> there are a
lot of extra flags to shrink the size of image. I just did a straight
cross-compile outside of OE and it looks to be okay. Thanks for your help.
2011/3/10 Julian Seward
>
> Strange that the link fails. It builds OK for
Hi,
I want to build a Valgrind tool which can instrument a multi-thread
program. It seems I can't use pthread library (such as
pthread_mutex_lock) directly in my tool. As to my understanding, when
the hosted program is a multi-thread program, the Valgrind tool's
code may race. So how can I loc
Strange that the link fails. It builds OK for me on Ubuntu 10.04
on ARM (Cortex-A8).
Do you have some custom CFLAGS? I see some gcc flags in there
that I don't immediately expect:
> -fexpensive-optimizations -fomit-frame-pointer -frename-registers
> -mthumb-interwork -mno-thumb
What happens i
> This is in an app that assembles and executes code, so it could be a
> genuine error.
Apps like that tend to die with very strange errors unless you run
with --smc-check=all. Did you do that?
J
--
Colocation vs. Mana
> valgrind and daemon exit shortly after launch, at some close but random
Have you tried --trace-children=yes ?
> One more. Valgrind also complains about unhandled system call, like that:
> That's a sigwait() system call:
That's difficult to fix because it interacts with the signals simulation.
2011/3/9 Piotr Adaszyński
> >
> > Strange. Does the output of "make -s regtest" on your setup match that
> > of the nightly PPC build (available in the valgrind-developers mailing
> > list archives) ?
> >
>
> Unfortunately, it's impossible to run "make -s regtest" and perform
> regression tests
