Re: gdb.mi/mi-cli.exp failures

Andrew Cagney
2003-04-01T17:09:53Z

> Hi Andrew,
>
>
>> Unfortunatly BFD changed an interface right in the middle of this -
>> it's put GDB/BFD into a death spiral :-(
>
>
> Die evil GDB die ... :-)
>
>
>> FAIL: gdb.base/relocate.exp: get address of static_bar (timeout)
>> FAIL: gdb.base/relocate.exp: static variables have different addresses
>> FAIL: gdb.base/relocate.exp: get address of global_foo (timeout)
>> FAIL: gdb.base/relocate.exp: get address of global_bar (timeout)
>> FAIL: gdb.base/relocate.exp: global variables have different addresses
>> FAIL: gdb.base/relocate.exp: get address of function_foo (timeout)
>> FAIL: gdb.base/relocate.exp: get address of function_bar (timeout)
>> FAIL: gdb.base/relocate.exp: functions have different addresses
>
>
> Hmm, I currently do not see these failures. In fact I do not see any
> failures running the relocate.exp script with the latest GDB and
> BINUTILS sources. Have you fixed something already ?

I see these failures on both i386 RH 7.2 native and PPC X d10v-elf using
a gdb+dejagnu source tree. It occures in both current and with a
2003-03-31-gmt tree containing just that simple.c change.

I should note that these are both elf + stab targets.

Andrew