From: Maciej Hrebien <m_hrebien@wp.pl>
To: linux-assembly@vger.kernel.org
Subject: Re: inside_SUB
Date: Thu, 19 Sep 2002 14:24:25 +0200 [thread overview]
Message-ID: <3D89C1F9.7D3DA7@wp.pl> (raw)
In-Reply-To: web-50089505@m1.plasa.com
ssams wrote:
>
> thanks for your replay
> this is make me learning more.
> But when i try to try, i found a new problem when i try to
> read
> the value from ecx after doing syscall read.
> mov $3,%eax
> mov $0,%ebx
> mov $6,%edx
>
> how can i read input from this code and reprinting it...?
> for example output:
> Enter e number: 4 #we enter 4
> you have number: 4 #reprinting
>
> help me please
> regard
> ssams
.data
char: .byte 0
.text
.globl _start
_start:
mov $3,%eax
xor %ebx,%ebx
mov $char,%ecx
mov $1,%edx
int $0x80
mov $4,%eax
inc %ebx
int $0x80
mov $1,%eax
int $0x80
Regards,
PS I recommend to read some tutorial(s) on how to write assembly code
useing Linux's calls.
--
Maciej Hrebien
next parent reply other threads:[~2002-09-19 12:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <web-50089505@m1.plasa.com>
2002-09-19 12:24 ` Maciej Hrebien [this message]
2002-09-16 5:15 inside_SUB ssams
2002-09-16 15:04 ` inside_SUB Maciej Hrebien
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=3D89C1F9.7D3DA7@wp.pl \
--to=m_hrebien@wp.pl \
--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).