[cdt-debug-dev] A patch in the CDT 1_0_1 branch

["Alain Magloire" <alain@xxxxxxx>]

I Would like to commit a patch in the 1_0_1 branch to make gdb less intruisive
when getting the register value.  This is a workaround, gdb hangs/crash
when getting register values. This particularly obvious on SH boards.
For example, just getting a register name that does not exists:

&"r\n"
^done,reason="breakpoint-hit",bkptno="1",thread-id="0",frame={addr="0x0804858c",func="main",args=[{name="argc",value="1"},{name="argv",value="0xbffff8cc"}],file="hello.c",line="20"}
(gdb) 
n
&"n\n"
^done,reason="end-stepping-range",thread-id="0",frame={addr="0x080485a9",func="main",args=[{name="argc",value="1"},{name="argv",value="0xbffff8cc"}],file="hello.c",line="21"}
(gdb) 
-data-list-register-names fjkj
^done,register-names=["eax"]
(gdb) 
-data-list-register-names 2000
^error,msg="bad register number"
(gdb) 
-data-list-register-names 2000
^error,msg="bad register number"
(gdb) 
-data-list-register-names 2000
^error,msg="bad register number"
(gdb) 
-data-list-register-names 2000
^error,msg="bad register number"
(gdb) 
-data-list-register-names 2000
&"ui-out.c:130: gdb-internal-error: push_level: Assertion `uiout->level >= 0 && uiout->level < MAX_UI_OUT_LEVELS' failed.\n"
~"An internal GDB error was detected.  This may make further\n"
~"debugging unreliable.  Quit this debugging session? (y or n) "


Note: 
- doing "data-list-register-names 2000" is done on purpose to make the error/bug obvious
- This is dealt with in cvs head, and PR in gdb affected 5.2.1 and up.