[cdt-dev] GDB, Valgrind and oprofile in non-standard locations (pathname

[Klaus Heinrich Kiwi <klausk@xxxxxxxxxxxxxxxxxx>]

I believe I successfully extended the GNU toolchain plugin to look for
my GCC, AR and AS binaries (using MBS).

But now I need to do the same to GDB, Valgrind and oprofile (those last
two from LTP, I know).

Anyone knows if there are extension points which would allow me to
specify my own debugger (my own gdb version), in the same way MBS allow
us to choose another toolchain?

Any pointers?

Thanks!

 -Klaus
-- 
Klaus Heinrich Kiwi             | klausk@xxxxxxxxxx 
IBM LTC Security Development    | http://blog.klauskiwi.com
http://www.ibm.com/linux/ltc    | http://www.ratliff.net/blog