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

Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=126883

[Timur Iskhodzhanov, 2012-03-12 14:55:43]

Hi Alexey, Evgeniy,

Can you please try locally for sanity checks and review this small CL?
I'm not a very experienced gdb user to estimate the sanity of the change (see
also the TEST= line for more info)

Thanks,
Timur

[alexeypa (please no reviews), 2012-03-12 18:51:52]

LGTM

[commit-bot: I haz the power, 2012-03-13 09:32:29]

No LGTM from a valid reviewer yet. Only full committers are accepted.
Even if an LGTM may have been provided, it was from a non-committer or
a lowly provisional committer, _not_ a full super star committer.
See http://www.chromium.org/getting-involved/become-a-committer
Note that this has nothing to do with OWNERS files.

[Timur Iskhodzhanov, 2012-03-13 10:05:11]

Alexander,

Can you please review to please the CQ?

Thanks,
Timur

[Timur Iskhodzhanov, 2012-03-15 08:28:56]

ping

[Alexander Potapenko, 2012-03-15 08:56:53]

LGTM

[commit-bot: I haz the power, 2012-03-15 08:57:02]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/timurrrr@chromium.org/9666056/1

[commit-bot: I haz the power, 2012-03-15 10:34:40]

Change committed as 126883