[PATCH, testsuite] Fix failures in gdb.mi/gdb2549.exp when register 0 doesn't have a name

[Luis Machado]

Hi,

This testcase only checks for the correct printing of registers via the 
mi command -data-list-register-values, not paying attention to register 
values, numbers or anything else.

Things work fine for targets that have register number 0 with a 
non-empty name. For other targets where register number 0 has an empty 
name, things break. As examples, we have a number of MIPS targets.

Such breakage happens because the logic for -data-list-register-values 
skips registers with empty names and proceeds to print the next register.

As an outcome, we start printing registers with numbers above 0, which 
is not something this testcase expects.

The following patch fixes this by completely ignoring the register 
number field.

Ok?

Luis
-------------- next part --------------
A non-text attachment was scrubbed...
Name: gdb2549.diff
Type: text/x-patch
Size: 1747 bytes
Desc: not available
URL: <http://sourceware.org/pipermail/gdb-patches/attachments/20130629/a47fbb2e/attachment.bin>