From: Brian Raiter <breadbox@muppetlabs.com>
To: linux-assembly@vger.kernel.org
Subject: Re: nasm -f bin / Elf format
Date: Wed, 22 Feb 2006 16:32:44 -0800 [thread overview]
Message-ID: <17405.684.517571.20396@eidolon.muppetlabs.com> (raw)
In-Reply-To: <200602222126.57346.thiago.silva@kdemail.net>
> Working gradualy, I tried to modify some data in a .data section,
> and got a segmentation fault.
You probably didn't set your the writable flag for the program section
that includes .data. If you created your program section header table
manually, make sure that p_flags (the second-to-last field) includes
the writable flag (4 = readable, 2 = writable, 1 = executable).
> Is that because there isn't a section header table with an entry
> indicating that the .data section is writable?
No, the section header table is not used when loading/executing ELF
binaries.
b
next prev parent reply other threads:[~2006-02-23 0:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-22 21:26 nasm -f bin / Elf format Thiago Silva
2006-02-23 0:32 ` Brian Raiter [this message]
2006-03-01 7:10 ` grub thing Aleph One
2006-03-01 13:34 ` Ricardo Nabinger Sanchez
2006-03-02 6:49 ` Aleph One
2006-03-01 14:42 ` Marcin Kościelnicki
2006-03-01 18:08 ` Ricardo Nabinger Sanchez
2006-03-02 6:46 ` Aleph One
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=17405.684.517571.20396@eidolon.muppetlabs.com \
--to=breadbox@muppetlabs.com \
--cc=linux-assembly@vger.kernel.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 NNTP newsgroup(s).