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: Mon, 24 Jun 2002 08:12:21 -0700 [thread overview]
Message-ID: <20020624081221.C30482@lucon.org> (raw)
In-Reply-To: <20020624150001.GA5373@branoic.them.org>; from dan@debian.org on Mon, Jun 24, 2002 at 11:00:01AM -0400
On Mon, Jun 24, 2002 at 11:00:01AM -0400, Daniel Jacobowitz wrote:
> On Mon, Jun 24, 2002 at 03:29:47PM +0200, Carsten Lange wrote:
> > Hi,
> >
> > I get the above error from gdb 5.2 when using the <file> command.
> > ...
> > (gdb) file iprbs
> > file iprbs
> > Reading symbols from iprbs...DW_FORM_strp pointing outside of .debug_str section
> > (gdb)
> > ...
> >
> > My mipsel-linux- toolchain consist of the following packages:
> > binutils-2.12.1
> > gcc-3.1
> > glibc-2.2.5
> > gdb-5.2
> >
> > I have no idea what the problem might be.
> >
> > Any hints (solutions/workaround) are welcome.
>
> Can you produce a testcase? These versions of the tools should not
> show the problem, assuming you rebuilt everything using them.
>
Please get the Linux binutils 2.12.90.0.12. You need that for gcc 3.1
on Linux/mips.
H.J.
next prev parent reply other threads:[~2002-06-24 15:09 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 [this message]
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
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=20020624081221.C30482@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox