The reason this is such a hard issue is because the automated attempt to build Chromium for armv6 failed, so the team didn't even have a chance to check for armv7 contamination. Sometimes packages will even build for armv6 with the automated code, but only to find out they have armv7 code in them on...

Apparently we can't edit our past posts, or if we can, I can't find it.

http://www.mail-archive.com/valgrind-us ... 03218.html

Another person working on the ARMv6 port.

Found this gem.

http://old.nabble.com/for-the-poor-armv ... 88031.html

If anybody gives this a shot, let post a reply here and let us know what you come up with. Otherwise, I'll give it a shot as soon as I can.

I'm starting this thread to post some information collected in the hope that anybody who might be working on the Valgrind ARMv6 port might gleam some information from it, or perhaps contribute some of their own. Old Thread from Old Nabble: http://old.nabble.com/Does-Valgrind--3.6.0-(or-3.6.1)-suppor...

Registered on the Wiki as DanielFenton. If you're okay with my help, I'm ready to help document.

Donated. Thanks for the hard work, gents!

Shirro,

I'll take a look at this when I get back from work today. I'll pm you my details, I'd be very interested in helping get this package off the ground.