From: "Steve Graegert" <graegerts@gmail.com>
To: zaphod001@gmail.com
Cc: linux-c-programming@vger.kernel.org
Subject: Re: reading elf section data
Date: Mon, 12 Nov 2007 13:07:14 +0100 [thread overview]
Message-ID: <6a00c8d50711120407t7c0f39b9g3fb3b45fc630ef31@mail.gmail.com> (raw)
In-Reply-To: <47389D7E.5070508@gmail.com>
On Nov 12, 2007 7:37 PM, Gery <zaphod001@gmail.com> wrote:
>
> Steve Graegert wrote:
> > On Nov 12, 2007 11:55 AM, Glynn Clements <glynn@gclements.plus.com> wrote:
> >> Gery wrote:
> >>
> >>> How to read in human format data from elf section?
> >> Can you be more specific? What kind of data? What format?
> >
> > I stopped replying to messages like those from the OP. Demanding help
> > without providing a minimum of information is just annoying, but
> > doing so without any etiquette is simply rude.
> >
> > \Steve
> >
> > --
> >
> > Steve Grägert
> > DigitalEther.de
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-c-programming" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> >
> Just for my understanding :)
> What is OP?
> What is it wrong w/ my etiquette?
> PLease, help me to fix my mistakes.
>
Hi Gery,
Let's start with a greeting, you'll be welcome and you're done with
50% of the "etiquette".
The OP stands for "original poster" and refers to the thread starter.
Finally I like to conclude a post with a closing formula or just a
signature including your name. That's the second part of the
"etiquette".
What I mean by rude is that questions like "How to read ELF data?"
motivates no one to answer as we have to ask for clarification first.
If you'd have asked "How do I read custom ELF sections added by GCC
using C?" everyone knows exactly what you want just by being a bit
more accurate.
Regarding your original question: try readelf first. It'll probably
do the trick.
\Steve
--
Steve Grägert
DigitalEther.de
-
To unsubscribe from this list: send the line "unsubscribe linux-c-programming" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2007-11-12 12:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-12 13:36 reading elf section data Gery
2007-11-12 10:55 ` Glynn Clements
2007-11-12 11:29 ` Steve Graegert
2007-11-12 18:37 ` Gery
2007-11-12 12:07 ` Steve Graegert [this message]
2007-11-12 19:11 ` Gery
2007-11-12 18:25 ` Gery
2007-11-12 15:56 ` Glynn Clements
2007-11-13 15:22 ` Gery
2007-11-13 9:13 ` Kristof Provost
2007-11-13 16:22 ` Gery
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=6a00c8d50711120407t7c0f39b9g3fb3b45fc630ef31@mail.gmail.com \
--to=graegerts@gmail.com \
--cc=linux-c-programming@vger.kernel.org \
--cc=zaphod001@gmail.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;
as well as URLs for NNTP newsgroup(s).