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

Andrew Cagney
2003-04-01T15:08:44Z

>> Applying the attached to BFD fixes the problem ....
>
>
> Although applying it would be a bad idea because it reverts several
> bug fixes that plug memory leaks.

Leaky memory is a lesser evil to corrupt memory.

> Instead here is a version that removes the use of "concat()" inside
> dwarf2.c:concat_filename() which is a good thing, but which probably
> does not solve the problem that you encountered in GDB.
>
> Can you narrow down which part of David Heine's patch (altered by me)
> is causing you problems, or tell me which tests in GDB are now failing
> so that I can try to track it down myself.

Unfortunatly BFD changed an interface right in the middle of this - it's
put GDB/BFD into a death spiral :-( I'm currently reverting a directory
tree to see what can be seen ...

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

Andrew