valgrind.sh vs gdb: keep the registers in gdb in sync with the code.
valgrind.sh vs gdb: keep the registers in gdb in sync with the code.

This might come at a performance price but I don't think this is important for valgrind.sh
(please note the tests on the bots are started using a different runner)

BUG=113513
TEST=http://code.google.com/p/chromium/issues/detail?id=113513#c8

Review URL: http://codereview.chromium.org/9666056

git-svn-id: de016e52bd170d2d4f2344f9bf92d50478b649e0@126883 0039d316-1c4b-4281-b951-d872f2087c98

gavinp/chromium,yitian134/chromium,adobe/chromium,adobe/chromium,gavinp/chromium,adobe/chromium,adobe/chromium,adobe/chromium,yitian134/chromium,gavinp/chromium,ropik/chromium,ropik/chromium,ropik/chromium,yitian134/chromium,adobe/chromium,gavinp/chromium,gavinp/chromium,yitian134/chromium,yitian134/chromium,adobe/chromium,adobe/chromium,yitian134/chromium,ropik/chromium,gavinp/chromium,ropik/chromium,yitian134/chromium,yitian134/chromium,yitian134/chromium,gavinp/chromium,ropik/chromium,gavinp/chromium,adobe/chromium,gavinp/chromium,ropik/chromium,gavinp/chromium,adobe/chromium,ropik/chromium,yitian134/chromium,ropik/chromium,adobe/chromium