Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Carsten Lange <Carsten.Lange@detewe.de>
To: "'linux-mips@oss.sgi.com'" <linux-mips@oss.sgi.com>
Subject: mipsel-linux-gdb(5.2): DW_FORM_strp pointing outside of .debug_str  section
Date: Mon, 24 Jun 2002 15:29:47 +0200	[thread overview]
Message-ID: <3D171ECB.28F566C1@detewe.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 473 bytes --]

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.

Best regards,
	Carsten

[-- Attachment #2: Card for Carsten Lange --]
[-- Type: text/x-vcard, Size: 296 bytes --]

begin:vcard 
n:Lange;Carsten
tel;fax:+49 6104 4234
tel;work:+49 30 6104 4228
x-mozilla-html:FALSE
url:http://www.detewe.de
org:Cordless Technology A/S Berlin
adr:;;Koepenicker Str. 180;10997 Berlin;;;
version:2.1
email;internet:Carsten.Lange@detewe.de
x-mozilla-cpt:;0
fn:Carsten Lange
end:vcard

WARNING: multiple messages have this Message-ID (diff)
From: Carsten Lange <Carsten.Lange@detewe.de>
To: "'linux-mips@oss.sgi.com'" <linux-mips@oss.sgi.com>
Subject: mipsel-linux-gdb(5.2): DW_FORM_strp pointing outside of .debug_str section
Date: Mon, 24 Jun 2002 15:29:47 +0200	[thread overview]
Message-ID: <3D171ECB.28F566C1@detewe.de> (raw)
Message-ID: <20020624132947.6Mpa_k-BlOScz-HPLyyqB1wHAo-t6M4WLeP_-PyaJok@z> (raw)

[-- Attachment #1: Type: text/plain, Size: 473 bytes --]

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.

Best regards,
	Carsten

[-- Attachment #2: Card for Carsten Lange --]
[-- Type: text/x-vcard, Size: 296 bytes --]

begin:vcard 
n:Lange;Carsten
tel;fax:+49 6104 4234
tel;work:+49 30 6104 4228
x-mozilla-html:FALSE
url:http://www.detewe.de
org:Cordless Technology A/S Berlin
adr:;;Koepenicker Str. 180;10997 Berlin;;;
version:2.1
email;internet:Carsten.Lange@detewe.de
x-mozilla-cpt:;0
fn:Carsten Lange
end:vcard

             reply	other threads:[~2002-06-24 13:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-24 13:29 Carsten Lange [this message]
2002-06-24 13:29 ` mipsel-linux-gdb(5.2): DW_FORM_strp pointing outside of .debug_str section 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

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=3D171ECB.28F566C1@detewe.de \
    --to=carsten.lange@detewe.de \
    --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