On Tue, May 10, 2011 at 06:02:59PM +0300, Riku Voipio wrote: > On Tue, May 10, 2011 at 03:28:36PM +0200, Pierre Habouzit wrote: > > I'm mostly clueless about which arm CPU versions Debian is supposed to > > support, should I wrap valgrind in some shell script that checks if the > > CPU is recent enough to run valgrind and fail gracefully if not? and if > > thats a good idea, how can I know which arm version the CPU supports? > > debian support armv4t+. considering /usr/bin/valgrind is a shell script, > checking from cpu from there should be possible. I wouldn't worry much, > valgrind is a expert tool, and experts should be able understand why > valgrind isn't available for their cpu.
oh right valgrind is a shellscript already, and I could like loic suggest trap on SIGILL from the shellscript and fail with an error message in that case… I know people are supposed to "know" but if I can easily print an error message it's even better. Thanks to both of you, it's likely that the next valgrind will have that then. -- ·O· Pierre Habouzit ··O madco...@debian.org OOO http://www.madism.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
