This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: gdb.mi/mi-cli.exp failures
- From: Daniel Jacobowitz <drow at mvista dot com>
- To: Andrew Cagney <ac131313 at redhat dot com>
- Cc: Nick Clifton <nickc at redhat dot com>, carlton at math dot stanford dot edu,gdb <gdb at sources dot redhat dot com>, binutils at sources dot redhat dot com
- Date: Tue, 1 Apr 2003 10:18:09 -0500
- Subject: Re: gdb.mi/mi-cli.exp failures
- References: <ro14r5j1g87.fsf@jackfruit.Stanford.EDU> <3E88A369.6090403@redhat.com> <3E88AE3F.4030005@redhat.com> <m3brzqzfn5.fsf@workshop.nickc.cambridge.redhat.com> <3E89AB79.1060700@redhat.com>
On Tue, Apr 01, 2003 at 10:08:41AM -0500, Andrew Cagney wrote:
>
> >>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
On what target - I don't see these...
This looks like a crash in the same function that changed interface...
perhaps the memory leak fix for simple.c was wrong, although I can't
quite see why. By the way, adding or removing the NULL at the end is
all that GDB needs to do to work with both interfaces.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer