From: Simon Posnjak <simon.posnjak@siol.net>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb@sources.redhat.com
Subject: Re: ARM/Linux OSABI problems (was Re: breakpoints not working in gdbserver)
Date: Thu, 15 Aug 2002 01:09:00 -0000 [thread overview]
Message-ID: <1029398949.3361.54.camel@klada.dyndns.org> (raw)
In-Reply-To: <20020814131001.GA32550@nevyn.them.org>
On Wed, 2002-08-14 at 15:10, Daniel Jacobowitz wrote:
> ... wait! I know what's wrong. Does uClibc provide a .note.ABI-tag
> section, like glibc does? If not, that needs to be corrected, or GDB
> needs to find some other way to recognize uClibc binaries.
You're right(objdump):
arm-linux:
**********
Sections:
Idx Name Size VMA LMA File off Algn
0 .interp 00000013 000080f4 000080f4 000000f4 2**0
CONTENTS, ALLOC, LOAD, READONLY, DATA
1 .note.ABI-tag 00000020 00008110 00008110 00000110 2**4
CONTENTS, ALLOC, LOAD, READONLY, DATA
2 .hash 00000198 00008130 00008130 00000130 2**2
CONTENTS, ALLOC, LOAD, READONLY, DATA
3 .dynsym 000003f0 000082c8 000082c8 000002c8 2**2
CONTENTS, ALLOC, LOAD, READONLY, DATA
4 .dynstr 000001fd 000086b8 000086b8 000006b8 2**0
CONTENTS, ALLOC, LOAD, READONLY, DATA
5 .gnu.version 0000007e 000088b6 000088b6 000008b6 2**1
CONTENTS, ALLOC, LOAD, READONLY, DATA
6 .gnu.version_r 00000030 00008934 00008934 00000934 2**2
CONTENTS, ALLOC, LOAD, READONLY, DATA
7 .rel.got 00000008 00008964 00008964 00000964 2**2
CONTENTS, ALLOC, LOAD, READONLY, DATA
8 .rel.bss 00000020 0000896c 0000896c 0000096c 2**2
CONTENTS, ALLOC, LOAD, READONLY, DATA
9 .rel.plt 000001c0 0000898c 0000898c 0000098c 2**2
CONTENTS, ALLOC, LOAD, READONLY, DATA
10 .init 00000018 00008b4c 00008b4c 00000b4c 2**2
CONTENTS, ALLOC, LOAD, READONLY, CODE
11 .plt 00000390 00008b64 00008b64 00000b64 2**2
CONTENTS, ALLOC, LOAD, READONLY, CODE
12 .text 000047d8 00008ef4 00008ef4 00000ef4 2**2
CONTENTS, ALLOC, LOAD, READONLY, CODE
13 .fini 00000014 0000d6cc 0000d6cc 000056cc 2**2
CONTENTS, ALLOC, LOAD, READONLY, CODE
14 .rodata 00001564 0000d6e0 0000d6e0 000056e0 2**2
CONTENTS, ALLOC, LOAD, READONLY, DATA
15 .data 00000168 00016c44 00016c44 00006c44 2**2
CONTENTS, ALLOC, LOAD, DATA
16 .ctors 00000008 00016dac 00016dac 00006dac 2**2
CONTENTS, ALLOC, LOAD, DATA
17 .dtors 00000008 00016db4 00016db4 00006db4 2**2
CONTENTS, ALLOC, LOAD, DATA
18 .got 000000f0 00016dbc 00016dbc 00006dbc 2**2
CONTENTS, ALLOC, LOAD, DATA
19 .dynamic 000000a0 00016eac 00016eac 00006eac 2**2
CONTENTS, ALLOC, LOAD, DATA
20 .sbss 00000000 00016f4c 00016f4c 00006f50 2**0
CONTENTS
21 .bss 00004b24 00016f50 00016f50 00006f50 2**4
ALLOC
22 .comment 000001ee 00000000 00000000 00006f50 2**0
CONTENTS, READONLY
uclibc:
*******
Sections:
Idx Name Size VMA LMA File off Algn
0 .interp 00000014 000080d4 000080d4 000000d4 2**0
CONTENTS, ALLOC, LOAD, READONLY, DATA
1 .hash 00000704 000080e8 000080e8 000000e8 2**2
CONTENTS, ALLOC, LOAD, READONLY, DATA
2 .dynsym 00000fa0 000087ec 000087ec 000007ec 2**2
CONTENTS, ALLOC, LOAD, READONLY, DATA
3 .dynstr 00000824 0000978c 0000978c 0000178c 2**0
CONTENTS, ALLOC, LOAD, READONLY, DATA
4 .rel.bss 00000048 00009fb0 00009fb0 00001fb0 2**2
CONTENTS, ALLOC, LOAD, READONLY, DATA
5 .rel.plt 00000700 00009ff8 00009ff8 00001ff8 2**2
CONTENTS, ALLOC, LOAD, READONLY, DATA
6 .plt 00000e10 0000a6f8 0000a6f8 000026f8 2**2
CONTENTS, ALLOC, LOAD, READONLY, CODE
7 .text 00037560 0000b508 0000b508 00003508 2**2
CONTENTS, ALLOC, LOAD, READONLY, CODE
8 .rodata 0000ccd0 00042a68 00042a68 0003aa68 2**2
CONTENTS, ALLOC, LOAD, READONLY, DATA
9 .data 00000778 00057738 00057738 00047738 2**2
CONTENTS, ALLOC, LOAD, DATA
10 .got 00000390 00057eb0 00057eb0 00047eb0 2**2
CONTENTS, ALLOC, LOAD, DATA
11 .dynamic 00000078 00058240 00058240 00048240 2**2
CONTENTS, ALLOC, LOAD, DATA
12 .sbss 00000000 000582b8 000582b8 000482b8 2**0
CONTENTS
13 .bss 00007d20 000582b8 000582b8 000482b8 2**3
ALLOC
What do you think what would be the best solution? I liked the idea that
Andrew Cagney give:
> (gdb) set architecture <machine> <osabi>
>
>the user should be able to force the <osabi> so that they can extract
>themselves from situtations such as this.
I will do this if you think it is a good idea. (Plese give me some
pointers where to start becouse I'm new to gdb sources)
Regards Simon
--
Simon Posnjak
http://klada.dyndns.org
prev parent reply other threads:[~2002-08-15 8:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-13 15:30 breakpoints not working in gdbserver Simon Posnjak
2002-08-13 15:42 ` Daniel Jacobowitz
2002-08-14 6:09 ` ARM/Linux OSABI problems (was Re: breakpoints not working in gdbserver) Daniel Jacobowitz
2002-08-14 6:58 ` William A. Gatliff
2002-08-14 21:33 ` Andrew Cagney
2002-08-15 1:09 ` Simon Posnjak [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=1029398949.3361.54.camel@klada.dyndns.org \
--to=simon.posnjak@siol.net \
--cc=drow@mvista.com \
--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