From: Steven Rostedt <rostedt@goodmis.org>
To: "linux-os (Dick Johnson)" <linux-os@analogic.com>
Cc: Coywolf Qi Hunt <coywolf@gmail.com>,
7eggert@gmx.de, Ukil a <ukil_a@yahoo.com>,
linux-kernel@vger.kernel.org
Subject: Re: Need help in understanding x86 syscall
Date: Thu, 11 Aug 2005 13:26:27 -0400 [thread overview]
Message-ID: <1123781187.17269.77.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.61.0508111310180.15153@chaos.analogic.com>
On Thu, 2005-08-11 at 13:10 -0400, linux-os (Dick Johnson) wrote:
> On Thu, 11 Aug 2005, Coywolf Qi Hunt wrote:
> >>
> >
> > Also glibc support.
> >
> > --
> > Coywolf Qi Hunt
> > http://ahbl.org/~coywolf/
>
> Probably doesn't use int 0x80 at all.
$ objdump -Dhalpr /lib/libc.so.6 | egrep 'int *\$0x80' | wc
448 2240 20160
And a little snapshot:
000288d0 <__libc_sigsuspend>:
288d0: 55 push %ebp
288d1: 89 e5 mov %esp,%ebp
288d3: 57 push %edi
288d4: 56 push %esi
288d5: 53 push %ebx
288d6: e8 00 00 00 00 call 288db <__libc_sigsuspend+0xb>
288db: 5b pop %ebx
288dc: 81 c3 19 c7 0e 00 add $0xec719,%ebx
288e2: 8b 83 b4 32 00 00 mov 0x32b4(%ebx),%eax
288e8: 85 c0 test %eax,%eax
288ea: 75 23 jne 2890f <__libc_sigsuspend+0x3f>
288ec: b9 08 00 00 00 mov $0x8,%ecx
288f1: 8b 55 08 mov 0x8(%ebp),%edx
288f4: 87 d3 xchg %edx,%ebx
288f6: b8 b3 00 00 00 mov $0xb3,%eax
288fb: cd 80 int $0x80
288fd: 87 d3 xchg %edx,%ebx
288ff: 89 c6 mov %eax,%esi
28901: 3d 00 f0 ff ff cmp $0xfffff000,%eax
28906: 77 33 ja 2893b <__libc_sigsuspend+0x6b>
28908: 89 f0 mov %esi,%eax
2890a: 5b pop %ebx
2890b: 5e pop %esi
2890c: 5f pop %edi
2890d: 5d pop %ebp
2890e: c3 ret
288fb seems to use "int 0x80" and so do all the other system calls that
I inspected.
$ ls -l /lib/libc.so.6
lrwxrwxrwx 1 root root 13 2005-08-09 22:28 /lib/libc.so.6 -> libc-2.3.5.so
-- Steve
next prev parent reply other threads:[~2005-08-11 17:26 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4Ae73-6Mm-5@gated-at.bofh.it>
2005-08-11 13:41 ` Need help in understanding x86 syscall Bodo Eggert
2005-08-11 14:04 ` linux-os (Dick Johnson)
2005-08-11 14:31 ` Steven Rostedt
2005-08-11 15:13 ` Coywolf Qi Hunt
2005-08-11 15:22 ` Steven Rostedt
2005-08-11 15:28 ` linux-os (Dick Johnson)
2005-08-11 15:51 ` Steven Rostedt
2005-08-11 16:19 ` Steven Rostedt
2005-08-11 16:31 ` Coywolf Qi Hunt
2005-08-11 16:59 ` Coywolf Qi Hunt
2005-08-11 17:10 ` linux-os (Dick Johnson)
2005-08-11 17:26 ` Steven Rostedt [this message]
2005-08-11 17:33 ` Steven Rostedt
2005-08-11 17:57 ` linux-os (Dick Johnson)
2005-08-11 17:59 ` Zachary Amsden
2005-08-11 18:17 ` Steven Rostedt
2005-08-11 19:58 ` Zachary Amsden
2005-08-11 20:04 ` Steven Rostedt
2005-08-12 19:30 ` Jan Engelhardt
2005-08-11 17:46 ` linux-os (Dick Johnson)
2005-08-11 18:11 ` Steven Rostedt
2005-08-11 18:21 ` linux-os (Dick Johnson)
2005-08-11 19:00 ` Steven Rostedt
2005-08-11 20:39 ` Zwane Mwaikambo
2005-08-12 11:29 ` Bodo Eggert
2005-08-11 17:18 ` Steven Rostedt
2005-08-12 5:04 ` Jeff Carr
2005-08-12 5:30 ` Coywolf Qi Hunt
2005-08-12 10:34 ` Steven Rostedt
2005-08-12 10:40 ` Steven Rostedt
2005-08-11 14:05 ` Steven Rostedt
2005-08-11 23:25 ` Bodo Eggert
2005-08-11 5:39 Ukil a
2005-08-11 13:54 ` Steven Rostedt
2005-08-11 15:52 ` Zachary Amsden
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=1123781187.17269.77.camel@localhost.localdomain \
--to=rostedt@goodmis.org \
--cc=7eggert@gmx.de \
--cc=coywolf@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.com \
--cc=ukil_a@yahoo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.