public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: Nick Clifton <nickc@redhat.com>
Cc: carlton@math.stanford.edu, gdb <gdb@sources.redhat.com>,
	binutils@sources.redhat.com
Subject: Re: gdb.mi/mi-cli.exp failures
Date: Tue, 01 Apr 2003 15:08:00 -0000	[thread overview]
Message-ID: <3E89AB79.1060700@redhat.com> (raw)
In-Reply-To: <m3brzqzfn5.fsf@workshop.nickc.cambridge.redhat.com>


>> 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


  reply	other threads:[~2003-04-01 15:08 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-31 19:35 David Carlton
2003-03-31 20:22 ` Andrew Cagney
2003-03-31 21:08   ` Andrew Cagney
2003-03-31 21:20     ` Andrew Cagney
2003-04-01  1:09       ` Hans-Peter Nilsson
2003-04-01  1:38         ` Ian Lance Taylor
2003-04-01 10:18     ` Nick Clifton
2003-04-01 15:08       ` Andrew Cagney [this message]
2003-04-01 15:18         ` Daniel Jacobowitz
2003-04-01 16:22           ` Andrew Cagney
2003-04-01 16:34             ` Daniel Jacobowitz
2003-04-01 17:01               ` Andrew Cagney
2003-04-01 18:03                 ` Daniel Jacobowitz
     [not found]         ` <m31y0mxk8i.fsf@workshop.nickc.cambridge.redhat.com>
2003-04-01 17:09           ` Andrew Cagney
2003-04-01 18:23             ` Daniel Jacobowitz
2003-04-02 17:06               ` Nick Clifton
2003-04-02 17:13                 ` Daniel Jacobowitz
2003-04-02 17:21                 ` Ian Lance Taylor
2003-04-02 17:28                   ` Daniel Jacobowitz
2003-04-02 17:44                     ` Ian Lance Taylor
2003-04-02 18:05                       ` Daniel Jacobowitz
2003-04-02 20:39                         ` Ian Lance Taylor
2003-04-02 20:38                           ` Daniel Jacobowitz
2003-04-02 20:53                             ` Ian Lance Taylor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3E89AB79.1060700@redhat.com \
    --to=ac131313@redhat.com \
    --cc=binutils@sources.redhat.com \
    --cc=carlton@math.stanford.edu \
    --cc=gdb@sources.redhat.com \
    --cc=nickc@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).