From: "H . J . Lu" <hjl@lucon.org>
To: GDB <gdb@sources.redhat.com>, gcc@gcc.gnu.org
Subject: Re: Does gdb 5.2 support gcc 3.1.1 on Linux/mips?
Date: Sun, 02 Jun 2002 22:42:00 -0000 [thread overview]
Message-ID: <20020602224240.A17723@lucon.org> (raw)
In-Reply-To: <20020603050906.GA19164@branoic.them.org>; from drow@mvista.com on Mon, Jun 03, 2002 at 01:09:06AM -0400
[-- Attachment #1: Type: text/plain, Size: 1131 bytes --]
On Mon, Jun 03, 2002 at 01:09:06AM -0400, Daniel Jacobowitz wrote:
> > >
> > > Then could you check if the produced binary is incorrect? That error
> > > usually indicates linker error.
> >
> > Did you imply gdb 5.2 worked fine for you with gcc 3.1.1 running on
> > your mips platform? My Linux/mipsel gcc 3.1.1 seems to work ok
> > otherwise:
> >
> > http://gcc.gnu.org/ml/gcc-testresults/2002-06/msg00069.html
>
> I haven't tried it in a while, but 3.1 snapshots worked fine with 5.2
> release, yes.
>
I doubt it is a linker bug. I have a simple C file. I cross compiled
it to Linux/mipsel on Linux/x86 with gcc 3.1.1. I got
# gcc -g ~/tmp/s.c -o ~/tmp/s
# gcc -g ~/tmp/s.c -o ~/tmp/s.o -c
# readelf -dw ~/tmp/s.o > /dev/null
unsupported or unknown DW_CFA_17
# readelf -dw ~/tmp/s.o > /dev/null
unsupported or unknown DW_CFA_17
# gdb ~/tmp/s
...
DW_FORM_strp pointing outside of .debug_str section
It looks like a gcc/gas bug to me. Can you tell me what you get with
your gdb and readelf on the enclosed s.o and s as well as what you get
with s and s.o compiled from s.c with your gcc 3.1 mips compiler?
Thanks.
H.J.
[-- Attachment #2: s --]
[-- Type: application/octet-stream, Size: 15668 bytes --]
[-- Attachment #3: s.o --]
[-- Type: application/octet-stream, Size: 11612 bytes --]
[-- Attachment #4: s.c --]
[-- Type: text/plain, Size: 60 bytes --]
#include <stdio.h>
main ()
{
printf ("hello world\n");
}
next prev parent reply other threads:[~2002-06-03 5:42 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-02 14:36 H . J . Lu
2002-06-02 18:00 ` Daniel Jacobowitz
2002-06-02 19:43 ` H . J . Lu
2002-06-02 22:01 ` Daniel Jacobowitz
2002-06-02 22:05 ` H . J . Lu
2002-06-02 22:09 ` Daniel Jacobowitz
2002-06-02 22:42 ` H . J . Lu [this message]
2002-06-02 23:03 ` H . J . Lu
2002-06-02 23:10 ` H . J . Lu
2002-06-03 4:22 ` Daniel Berlin
2002-06-03 7:18 ` Daniel Jacobowitz
2002-06-03 8:55 ` DW_CFA_def_cfa_offset_sf bug? (Re: Does gdb 5.2 support gcc 3.1.1 on Linux/mips?) H . J . Lu
[not found] ` <20020603092959.A27426@lucon.org>
[not found] ` <20020603104131.A28590@lucon.org>
[not found] ` <20020603115703.A29881@lucon.org>
[not found] ` <20020604003246.C20867@sunsite.ms.mff.cuni.cz>
[not found] ` <20020603153716.A1294@lucon.org>
2002-06-03 16:25 ` PATCH: Use stabs for Linux/mips (Re: binutils is broken on ELF/MIPS) H . J . Lu
2002-06-03 16:41 ` Daniel Jacobowitz
2002-06-03 16:51 ` H . J . Lu
2002-06-03 17:43 ` Richard Henderson
2002-06-03 19:52 ` Doug Evans
2002-06-03 19:54 ` H . J . Lu
2002-06-03 20:36 ` Richard Henderson
2002-06-03 17:50 ` Eric Christopher
2002-06-03 18:03 ` H . J . Lu
2002-06-03 18:29 ` Eric Christopher
2002-06-03 19:47 ` H . J . Lu
2002-06-03 18:40 ` Daniel Jacobowitz
2002-06-03 19:51 ` H . J . Lu
2002-06-03 20:23 ` Daniel Jacobowitz
2002-06-03 20:28 ` H . J . Lu
2002-06-04 13:18 ` Eric Christopher
2002-06-02 23:30 ` Does gdb 5.2 support gcc 3.1.1 on Linux/mips? Jakub Jelinek
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=20020602224240.A17723@lucon.org \
--to=hjl@lucon.org \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sources.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