> I am validating valgrind options for MIPS platform. Does it make sense to > validate these option for MIPS platform:
Please explain the meaning of "validating options". What is the goal, and how are you attempting to do it? Why is the goal desirable? Just invoking "valgrind <options> /bin/date" is enough to check that valgrind accepts those options. That is one meaning of validating the options. > 1)--smc-check=<none|stack|all|all-non-file> [default: stack] > > 2)--show-emwarns=<yes|no> [default: no] > > 3)--sim-hints=hint1,hint2,... > > 4)--fair-sched=<no|yes|try> [default: no] > > 5)--kernel-variant=variant1,variant2,... > > 6)--soname-synonyms=syn1=pattern1,syn2=pattern2,.. Except for --kernel-variant=, each of those six options readily applies to all architectures. --kernel-variant= likely applies only for x86 and/or x86_64. Download the user manual, then search the manual for the name of the option. Even better, act like a developer: check out a source code tree, and search the source code (including the source to the documentation) for the name of the option. You can also look at the internal test cases to see how they use the option. -- ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
