linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mohana Sundaram <ksmoha@gmail.com>
To: beginner_h4x3r <nightdecoder@gmail.com>
Cc: Rahul K Patel <rahulk.patel@einfochips.com>,
	linux-c-programming@vger.kernel.org
Subject: Re: Linux process...
Date: Mon, 30 Mar 2009 12:41:38 +0530	[thread overview]
Message-ID: <7fd0b9b40903300011o6aa51396l73873553cf09f2e7@mail.gmail.com> (raw)
In-Reply-To: <34e1241d0903292357ha2fb36av5480578eddc1c67d@mail.gmail.com>

Please read about virtual memory.. In a nutshell the printed addresses
are virtual addresses not absolute addresses.

Thanks,
- Mohan.
The expert at anything was once a beginner.




On Mon, Mar 30, 2009 at 12:27, beginner_h4x3r <nightdecoder@gmail.com> wrote:
> Hi Rahul,
>
> What is the means of process's base address and offset? It's means
> child's base address is offset? how to know child's process stack_int
> address in my demonstration code.
>
> Thanks in advance.
>
> --- curious_hacker
>
> On Mon, Mar 30, 2009 at 1:15 PM, Rahul K Patel
> <rahulk.patel@einfochips.com> wrote:
>> it's offset address and not absolute address.
>> base addresses of your parent and child process will be different so
>> final absolute address (base + offset) will be different for both.
> --
> 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
>
--
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

  reply	other threads:[~2009-03-30  7:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-30  6:06 Linux process beginner_h4x3r
2009-03-30  6:15 ` Rahul K Patel
2009-03-30  6:57   ` beginner_h4x3r
2009-03-30  7:11     ` Mohana Sundaram [this message]
2009-03-30 11:36 ` Fabian Ischia
2009-03-31  1:12   ` beginner_h4x3r
2009-03-31  5:57     ` Glynn Clements
2009-03-31 23:45     ` stephan

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=7fd0b9b40903300011o6aa51396l73873553cf09f2e7@mail.gmail.com \
    --to=ksmoha@gmail.com \
    --cc=linux-c-programming@vger.kernel.org \
    --cc=nightdecoder@gmail.com \
    --cc=rahulk.patel@einfochips.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).