From: Chris Friesen <cfriesen@nortelnetworks.com>
To: sting sting <zstingx@hotmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: do_brk() trace mystery
Date: Fri, 12 Mar 2004 15:11:26 -0500 [thread overview]
Message-ID: <4052196E.3010304@nortelnetworks.com> (raw)
In-Reply-To: <Sea2-F60clKZMX3rQvx00046766@hotmail.com>
sting sting wrote:
> But I did a search on the kernel tree fo do_brk()
> and I found only 5 entries (in 2.6 kernel and also in 2.4.24).
> One of the was the declaration in mm.h; the other was
> implementation in mmap.c
You probably want sys_brk().
> So the mystery is : who calls the brk() system call when I type
> "cat /proc/interrupts"
cat calls malloc(), glibc calls brk(), kernel does sys_brk()
Chris
--
Chris Friesen | MailStop: 043/33/F10
Nortel Networks | work: (613) 765-0557
3500 Carling Avenue | fax: (613) 765-2986
Nepean, ON K2H 8E9 Canada | email: cfriesen@nortelnetworks.com
prev parent reply other threads:[~2004-03-12 20:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-12 19:39 do_brk() trace mystery sting sting
2004-03-12 20:11 ` Chris Friesen [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=4052196E.3010304@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zstingx@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