Hi all,
As a bit of a test for myself, I'm trying to run openstack tests on top
of the mostly-ready PSCI support the virtualization team has been
working on. I've built myself an Ubuntu kernel with the needed patches
(actually all of kvm/next) and now need a matching qemu. I fished these
patches:
http://lists.gnu.org/archive/html/qemu-devel/2014-05/msg04514.html
out of patchwork and applied them on top of the qemu that's in trusty
but it fails to build. I guess these patches depends that are in qemu
git but not in 2.0.0? In any case, before I dive into trying to fix
this myself, does anyone have binaries or even better debs with those
patches in?
Cheers,
mwh
Hi!
I'm trying to use valgrind on an a15, 32 hf environment obviously.
I have -g on with no optimization for all my code that is being run.
Command line options for valgrind are:
valgrind -v --tool=memcheck --leak-check=full --show-reachable=yes
--leak-resolution=high --track-origins=yes --num-callers=10 ./matvec
I've tried num-callers as high as 50 it makes no difference. I get
almost zero information when it comes to leaks and the call stack. Ok
great it's nice to see things broken down between malloc and new and
so on. But without a call stack this is pretty worthless.
snippet:
==19013== 1,937,944 bytes in 18,389 blocks are still reachable in loss
record 8 of 9
==19013== at 0x482DE80: operator new(unsigned int) (in
/usr/lib/valgrind/vgpreload_memcheck-arm-linux.so)
==19013==
==19013== 4,524,046 bytes in 14,368 blocks are still reachable in loss
record 9 of 9
==19013== at 0x482E420: malloc (in
/usr/lib/valgrind/vgpreload_memcheck-arm-linux.so)
==19013==
==19013== LEAK SUMMARY:
==19013== definitely lost: 328 bytes in 6 blocks
==19013== indirectly lost: 396 bytes in 3 blocks
==19013== possibly lost: 808 bytes in 26 blocks
==19013== still reachable: 8,342,474 bytes in 37,405 blocks
==19013== suppressed: 0 bytes in 0 blocks
Did I miss an option? or something obvious which would output more information ?
Thanks!
--
Regards,
Tom
"Where's the kaboom!? There was supposed to be an earth-shattering
kaboom!" Marvin Martian
Tech Lead, Graphics Working Group | Linaro.org │ Open source software
for ARM SoCs
w) tom.gall att linaro.org
h) tom_gall att mac.com
== Progress ==
* bug 1328776 "ll-20140607.0 - ftbfs on beaglebone" (CARD-788, 15%)
* did the planned updates to llct, updated the schedule for ll updates in 2014.06 (CARD-788, 5%)
* time off (80%)
== Plans ==
* linux-linaro kernel release week (CARD-788)
* follow up on:
. DEVPLAT-210 "upstream: fastboot in u-boot"
. bug 1189839 "kernel crash on arndale while CPU hotplug"
* create a topic branch for ll with the recently posted patch set for the "Add ILP32 support for ARM64 to Linaro engineering
builds" card (CARD-1161)
* update the wiki doc for DEVPLAT-204
== Issues ==
* none
== Progress ==
* Built qtchooser, qtwebkit, boost1.55, raptor (DEVPLAT-217: 45%)
* Rebuilt packages in gnutls28 transition (DEVPLAT-217: 15%)
* Fix/build eglibc2.19 (DEVPLAT-221: 10%)
* Learned how to drive wanna-build and wb (DEVPLAT-221: 10%)
* Gave back ~40 packages that had temporary failures (DEVPLAT-221: 10%)
* Worked on arm64 NMU process with Chen (DEVPLAT-221: 5%)
* Some bootstrap sprint organising (5%)
== Plans ==
* Fix/Build soprano (DEVPLAT-217)
* NMU pile of packages
* Test Arm64 rootfs on ARM hardware
== Issues ==
Wookey
--
Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM
http://wookware.org/
== Progress ==
* Fixed all known problems with the Android toolchain (DEVPLAT-101(?), 70%)
* Android toolchain release (DEVPLAT-101(?), 5%)
* Worked on NDK build scripts (DEVPLAT-101(?), 10%)
* Started on toolchain binary release (DEVPLAT-101, 10%)
* Assorted fixes, documentation issues, meetings (untracked, 5%)
== Plans ==
* Finish toolchain binary release (DEVPLAT-101)
* Finish porting AArch64 Bionic optimizations to ARMv7 (DEVPLAT-104)
* Investigate more functions that can be optimized in Bionic on both v8 and
v7 (JUICE-298)
== Issues ==
* Not sure if DEVPLAT-101 covers everything I'm attributing to it (NDK
releases etc.), need to clarify or create more cards.