|
From: timmins <tim...@ov...> - 2014-03-10 16:21:27
|
Hi all, I’m new to Valgrind, so forgive me if I’m missing something obvious. I am attempting to build Valgrind for the MIPS64-based Cavium Octeon CN52xx. We have a slightly unusual configuration with respect to using a 64-bit toolchain and kernel, but our target runs 32-bit apps with 32-bit libraries (we compile them with the –mabi=n32 flag). Configuring as follows: Valgrind builds and runs, but fails to allocate memory for a superblock: ulimit shows there are no relevant limits imposed: Running strace on Valgrind reveals the following error: I'm surprised at seeing the n64_* syscalls, after compiling with the mabi=n32 flag. We have 2GB swap available, ~750MB RAM free, and I can malloc the same requested amount of memory several times over from a C app with no problem. Some observations: - There were many “cast from pointer to integer of different size” warnings during compilation. I wonder if this is because I’m compiling as N32, and Valgrind is expecting this to be a 64-bit target application. - Our toolchain is fairly old (gcc 4.3.3). using the –mplt compiler option makes no difference. Any suggestions would be greatly appreciated. Many thanks, Tim -- View this message in context: http://valgrind.10908.n7.nabble.com/Valgrind-13854-Cross-compiling-for-Cavium-MIPS64-N32-ABI-tp48980.html Sent from the Valgrind - Dev mailing list archive at Nabble.com. |