All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. J. Lu" <hjl@lucon.org>
To: Daniel Jacobowitz <dan@debian.org>
Cc: Carsten Lange <Carsten.Lange@detewe.de>,
	"'linux-mips@oss.sgi.com'" <linux-mips@oss.sgi.com>
Subject: Re: mipsel-linux-gdb(5.2): DW_FORM_strp pointing outside of .debug_str section
Date: Tue, 25 Jun 2002 08:22:46 -0700	[thread overview]
Message-ID: <20020625082246.A18907@lucon.org> (raw)
In-Reply-To: <20020625131608.GB13216@branoic.them.org>; from dan@debian.org on Tue, Jun 25, 2002 at 09:16:08AM -0400

On Tue, Jun 25, 2002 at 09:16:08AM -0400, Daniel Jacobowitz wrote:
> > 
> > Please get the Linux binutils 2.12.90.0.12. You need that for gcc 3.1
> > on Linux/mips.
> 
> Would you mind explaining what binutils patch affected the DW_FORM_strp
> problems?  Was it a SEC_MERGE bug that I recall being recently
> discussed.

Yes:

http://sources.redhat.com/ml/binutils/2002-06/msg00111.html

Please test it as much as you can. I want to make sure it is 100%
correct. Also as Daniel said, you need gcc 3.1 branch from CVS to
get gdb working with dwarf.


H.J.

      reply	other threads:[~2002-06-25 15:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-24 13:29 mipsel-linux-gdb(5.2): DW_FORM_strp pointing outside of .debug_str section Carsten Lange
2002-06-24 13:29 ` Carsten Lange
2002-06-24 15:00 ` Daniel Jacobowitz
2002-06-24 15:12   ` H. J. Lu
2002-06-25 11:06     ` Carsten Lange
2002-06-25 11:06       ` Carsten Lange
2002-06-25 13:15       ` Daniel Jacobowitz
2002-06-25 15:39       ` H. J. Lu
2002-06-26  5:09         ` Carsten Lange
2002-06-26  5:09           ` Carsten Lange
2002-06-26  5:58           ` H. J. Lu
2002-06-25 13:16     ` Daniel Jacobowitz
2002-06-25 15:22       ` H. J. Lu [this message]

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=20020625082246.A18907@lucon.org \
    --to=hjl@lucon.org \
    --cc=Carsten.Lange@detewe.de \
    --cc=dan@debian.org \
    --cc=linux-mips@oss.sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.