linux-assembly.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Hilst <danielhilst@gmail.com>
Cc: linux-assembly@vger.kernel.org
Subject: Re: Declare strings on stack, gas
Date: Thu, 19 Apr 2012 16:07:31 +0000	[thread overview]
Message-ID: <4F903843.5080001@gmail.com> (raw)
In-Reply-To: <4F8F174F.3080205@sonoma.edu>

On 04/18/2012 07:34 PM, Robert Plantz wrote:
> On 4/18/2012 7:58 AM, Daniel Hilst wrote:
>> Is possible to declare strings on stack? I'm using mov + ebp offsets
>> to do something like that.. Is there an easier way to do it?
>>
>> Here is an sample off how I'm doing it: http://sprunge.us/UUZI
>>
>> The hex numbers are a "Hello World" string..
>> I have tried .assci without success :(
>>
>> Thanks in advance!
>>
>>
> Basically, you're asking if the compiler/assembler can initialize the
> stack to some known value. Since memory on the stack is dynamically
> allocated by the instructions:
>
> doit:
> push %ebp ; Save caller's base pointer
> mov %esp, %ebp ; Establish our base pointer
>
> sub $12, %esp ; Allocate memory on the stack
>
>
>
> the answer is 'no.' After you allocate stack memory (which now has
> garbage values), you need to copy known values there. Write your code in
> C and use the '-S' gcc option to see how the compiler does this. The
> '-S' option will generate the assembly language file foo.s from the C
> source file foo.c.
>
> --Bob
>
>
>

Thanks guys, the closest I got was use .text section and the %esi trick.
Now I know about stack dynamics.

Cheers!
-- 
Follow the white rabbit!

      reply	other threads:[~2012-04-19 16:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-18 14:58 Declare strings on stack, gas Daniel Hilst
2012-04-18 18:14 ` JIA Zhongye
2012-04-18 19:34 ` Robert Plantz
2012-04-19 16:07   ` Daniel Hilst [this message]

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=4F903843.5080001@gmail.com \
    --to=danielhilst@gmail.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).