From: willy meier <wklux@yahoo.co.uk>
To: Jason Roberts <v3ct0r99@hotmail.com>
Cc: linux-assembly@mlists.in-berlin.de, linux-assembly@vger.kernel.org
Subject: Re: confused asm newbie
Date: Thu, 23 Oct 2003 15:38:39 +0100 [thread overview]
Message-ID: <3F97E7EF.CE5E0F19@yahoo.co.uk> (raw)
In-Reply-To: Law9-F40TZiqpJjmH4P000039ed@hotmail.com
Jason Roberts wrote:
>
> I have a few questions concerning how the stack is used and how memory is
> accessed
> and what it looks like.I've read books, which only serve to confuse me, or
> the author tries
> to mystify you into believing assembly is dark magic only for the elite.
don't get discuraged by those utterly stupid people...
I hope, the following helps to de-mystify:
"Machine-Level Representations of C Programs on Linux/IA32",
http://www.lxhp.in-berlin.de/lhplinks.html#cas
also, the System-V & POSIX documents specify the C to asm translation,
http://www.lxhp.in-berlin.de/lhplinks.html#sysv
and, if you compile with the following options to the assembler, you'll
get the complete asm listing from compiling a C program, piped into the
file 'LOG.m':
CFLAGS += -Wa,-acdlms -save-temps
make (or 'cc' or any other appropriate command) 2>&1 | tee -a LOG.m
tracing with the 'ald' debugger and tests with 'strace' and 'ltrace'
would also return much information about programs execution (links on
above mentioned page).
best,
hp
--
Linux,Assembly,Forth: http://www.lxhp.in-berlin.de/index-lx.shtml
>> xxxx -at- lxhp -dot- in-berlin -dot- de <<
next prev parent reply other threads:[~2003-10-23 14:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-23 12:03 confused asm newbie Jason Roberts
2003-10-23 12:53 ` Frederic Marmond
2003-10-23 14:38 ` willy meier [this message]
2003-10-23 15:50 ` Philip Jacob Smith
2003-11-01 17:07 ` GRUB sample kernel question ram
2003-11-01 21:24 ` Alexander Jänicke
2003-11-01 22:36 ` ram
2003-11-17 11:47 ` confused asm newbie b klein
2003-11-17 12:29 ` Frederic Marmond
2003-11-17 13:18 ` b klein
2003-11-17 13:36 ` Frederic Marmond
2003-11-18 2:51 ` Philip Jacob Smith
2003-11-20 21:52 ` b klein
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=3F97E7EF.CE5E0F19@yahoo.co.uk \
--to=wklux@yahoo.co.uk \
--cc=linux-assembly@mlists.in-berlin.de \
--cc=linux-assembly@vger.kernel.org \
--cc=v3ct0r99@hotmail.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).