linux-assembly.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Colannino <james@colannino.org>
To: linux-assembly@vger.kernel.org
Subject: More about stacks
Date: Wed, 14 Sep 2005 14:14:53 -0700	[thread overview]
Message-ID: <432892CD.3090907@colannino.org> (raw)

First, I just wanted to ask and see if anyone here on the list has any 
reading recommendations to help me understand the stack in detail as 
well as the details about how memory is addressed and interacted with 
via 386 32-bit protected mode.

The question I wanted to ask the list was that I know when you want to 
expand the stack to make room for more data (particularly when you're 
setting up local variables in C) you simply do a sub on %esp, but my 
question is, how do you know when you do this that you aren't violating 
data from some other process, or maybe even data belonging to other 
sections of your code, .data for example.  Thanks :)

James

             reply	other threads:[~2005-09-14 21:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-14 21:14 James Colannino [this message]
2005-09-14 23:07 ` More about stacks Richard Cooper
2005-09-20  1:45   ` Herbert Poetzl
2005-09-15 14:19 ` Stephen Pelc

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=432892CD.3090907@colannino.org \
    --to=james@colannino.org \
    --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).