From: "Bhushan Verma" <bhushan.verma@iap-online.com>
To: <binutils@sourceware.org>
Subject: Regarding linker code generation
Date: Mon, 30 Jul 2007 14:24:00 -0000 [thread overview]
Message-ID: <OIEOKFKBHBJGOGBPDDFICEPPCAAA.bhushan.verma@iap-online.com> (raw)
In-Reply-To: <1185763943.19324.ezmlm@sourceware.org>
Dear ALL,
Could you please help me to sort out my problem.
Actually whenever I run my run time linker on unix like OS (arm) with
following Program header
This run well.
Program Header[0]:
p_vaddr: 0 p_flags: [ PF_X PF_W PF_R ]
p_paddr: 0 p_type: [ PT_LOAD ]
p_filesz: 0x2bc1f p_memsz: 0x2d6c8
p_offset: 0 p_align: 0x8000
Why linker is generating this type of header?
But whenwver I separate code and data segment this gives segmentation fault
inside self relocation of run time linker.
after separation of code and data segment of run timer linker:
Program Header[0]:
p_vaddr: 0 p_flags: [ PF_X PF_R ]
p_paddr: 0 p_type: [ PT_LOAD ]
p_filesz: 0x2b094 p_memsz: 0x2b094
p_offset: 0 p_align: 0x8000
Program Header[1]:
p_vaddr: 0x330a4 p_flags: [ PF_W PF_R ]
p_paddr: 0x330a4 p_type: [ PT_LOAD ]
p_filesz: 0xa2b p_memsz: 0x24d4
p_offset: 0x2b0a4 p_align: 0x8000
I am using gnu arm toolchain
Could you please help me is this due to permiison of data segment or I have
some other problem as in creating wrong data segment etc.
could you please explian me p_vaddr Vs p_paddr.
Regards
Verma
next parent reply other threads:[~2007-07-30 3:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1185763943.19324.ezmlm@sourceware.org>
2007-07-30 14:24 ` Bhushan Verma [this message]
2007-08-01 17:38 ` Nick Clifton
2007-08-02 1:21 ` Bhushan Verma
2007-08-06 15:28 ` Nick Clifton
2007-08-13 7:45 ` Bhushan Verma
2007-08-31 20:53 ` Nick Clifton
2007-09-04 8:23 ` Bhushan Verma
2007-09-07 15:38 ` Nick Clifton
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=OIEOKFKBHBJGOGBPDDFICEPPCAAA.bhushan.verma@iap-online.com \
--to=bhushan.verma@iap-online.com \
--cc=binutils@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).