gdb.mi/mi-var-display.exp failure

[Ulrich Weigand]

FAIL: gdb.mi/mi-var-display.exp: create variable a2 in different scope
FAIL: gdb.mi/mi2-var-display.exp: create variable a2 in different scope

Needs further analysis.

[Yao Qi (yao-codesourcery)]

[CodeSourcery #3779, #3276]

[Ulrich Weigand (uweigand)]

The test case assumes that $fp returns a frame-base value that can in turn be used as argument to var-create to identify a particular frame to create a variable object in.

However, the ARM back-end overrides $fp to always display the value of register 11. In particular for Thumb code, the contents of register 11 are completely unrelated to that frame base value ...

[Yao Qi (yao-codesourcery)]

Yes, GDB ARM back-end treats always $fp as r11, even in Thumb mode. The expected behavior should be fp is mapped to r7 in Thumb mode, while to r11 in ARM mode.

Current GDB has no such capability without changing some target-independent part.

Patch is submitted http://sourceware.org/ml/gdb-patches/2010-12/msg00286.html