Thanks for your reply. I am happy to report that adding
--vex-iropt-register-updates=allregs-at-mem-access
option to callgrind worked for me and I am able to run it without any
problems. I think the issue was that JVM generates a lot of SIGSEGV signals
during it's "normal" course of operation and v
> I am trying to profile an application with callgrind. The application
> uses hadoop's libhdfs api which in turn makes JNI calls to a JVM. This
> causes a crash in the JVM. When running normally the application seems
> to work fine.
>
> I am running on Centos 6.7 with Valgrind 3.11.0. Java is 1.8
On 02/08/16 22:30, Eqbal wrote:
>> valgrind -v --tool=callgrind --dump-instr=yes --trace-jump=yes
>> --trace-children=yes --smc-check=all --collect-jumps=yes
>> --simulate-cache=yes ./example
Try adding --px-default=allregs-at-mem-access. If that doesn't help
then try --px-default=allregs-at-eac
Hi,
I haven't got a response to this. I am a new to Valgrind. Any pointers
would be greatly appreciated.
Thanks.
On Sun, Jul 10, 2016 at 6:18 PM, Eqbal wrote:
> I am trying to profile an application with callgrind. The application uses
> hadoop's libhdfs api which in turn makes JNI calls to a
I am trying to profile an application with callgrind. The application uses
hadoop's libhdfs api which in turn makes JNI calls to a JVM. This causes a
crash in the JVM. When running normally the application seems to work fine.
I am running on Centos 6.7 with Valgrind 3.11.0. Java is 1.8 Oracle JDK
