From: "Maciej W. Rozycki" <macro@codesourcery.com>
To: Luis Machado <lgustavo@codesourcery.com>
Cc: Pedro Alves <palves@redhat.com>, Tom Tromey <tromey@redhat.com>,
Stan Shebs <stanshebs@earthlink.net>,
GDB Patches <gdb-patches@sourceware.org>,
Ulrich Weigand <uweigand@de.ibm.com>
Subject: Re: [PATCH, testsuite] Don't run SREC, IHEX and TEKHEX tests for MIPS N64.
Date: Thu, 04 Jul 2013 12:13:00 -0000 [thread overview]
Message-ID: <alpine.DEB.1.10.1307041303580.20590@tp.orcam.me.uk> (raw)
In-Reply-To: <51D56120.1040001@codesourcery.com>
On Thu, 4 Jul 2013, Luis Machado wrote:
> > Try -Ttext-segment=... instead, sorry about the confusion.
>
> That also doesn't seem to prevent thing from being linked at addresses >
> 32-bits. Code is still at 0x120000000 apparently.
>
> (gdb) break checkpoint1^M
> Breakpoint 1 at 0x120000cdc: file gdb/testsuite/gdb.base/dump.c, line 19.
Works for me:
$ cat text.c
int main(void)
{
return 0;
}
$ mips-linux-gnu-gcc -mabi=64 -O2 -Wl,-Ttext-segment=0x12340000 -o text text.c
$ mips-linux-gnu-readelf -l text
Elf file type is EXEC (Executable file)
Entry point 0x123407c0
There are 7 program headers, starting at offset 64
Program Headers:
Type Offset VirtAddr PhysAddr
FileSiz MemSiz Flags Align
PHDR 0x0000000000000040 0x0000000012340040 0x0000000012340040
0x0000000000000188 0x0000000000000188 R E 8
INTERP 0x0000000000000ab0 0x0000000012340ab0 0x0000000012340ab0
0x000000000000000f 0x000000000000000f R 1
[Requesting program interpreter: /lib64/ld.so.1]
LOAD 0x0000000000000000 0x0000000012340000 0x0000000012340000
0x0000000000000ae4 0x0000000000000ae4 R E 10000
LOAD 0x0000000000000ae8 0x0000000012350ae8 0x0000000012350ae8
0x00000000000000f0 0x0000000000000108 RW 10000
DYNAMIC 0x0000000000000330 0x0000000012340330 0x0000000012340330
0x00000000000001b0 0x00000000000001b0 RWE 8
NOTE 0x0000000000000ac4 0x0000000012340ac4 0x0000000012340ac4
0x0000000000000020 0x0000000000000020 R 4
NULL 0x0000000000000000 0x0000000000000000 0x0000000000000000
0x0000000000000000 0x0000000000000000 8
Section to Segment mapping:
Segment Sections...
00
01 .interp
02 .MIPS.options .dynamic .hash .dynsym .dynstr .gnu.version .gnu.version_r .init .text .MIPS.stubs .fini .rodata .interp .eh_frame .note.ABI-tag
03 .ctors .dtors .jcr .data .rld_map .got .sdata .bss
04 .dynamic
05 .note.ABI-tag
06
$
Maciej
next prev parent reply other threads:[~2013-07-04 12:13 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-01 16:24 Luis Machado
2013-07-02 14:37 ` Yao Qi
2013-07-02 14:45 ` Luis Machado
2013-07-03 0:03 ` Yao Qi
2013-07-02 16:47 ` Tom Tromey
2013-07-02 16:51 ` Luis Machado
2013-07-02 17:19 ` Stan Shebs
2013-07-02 18:10 ` Tom Tromey
2013-07-02 18:50 ` Luis Machado
2013-07-02 20:55 ` Tom Tromey
2013-07-03 15:05 ` Pedro Alves
2013-07-03 19:23 ` Luis Machado
2013-07-03 19:26 ` Pedro Alves
2013-07-03 20:19 ` Luis Machado
2013-07-04 8:11 ` Pedro Alves
2013-07-06 2:41 ` Luis Machado
2013-07-03 20:35 ` Maciej W. Rozycki
2013-07-03 20:54 ` Luis Machado
2013-07-03 21:08 ` Maciej W. Rozycki
2013-07-04 11:48 ` Luis Machado
2013-07-04 12:13 ` Maciej W. Rozycki [this message]
2013-07-04 12:21 ` Luis Machado
2013-07-04 13:22 ` Ulrich Weigand
2013-07-04 13:24 ` Luis Machado
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=alpine.DEB.1.10.1307041303580.20590@tp.orcam.me.uk \
--to=macro@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=lgustavo@codesourcery.com \
--cc=palves@redhat.com \
--cc=stanshebs@earthlink.net \
--cc=tromey@redhat.com \
--cc=uweigand@de.ibm.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