Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 9 Feb 2003 13:36:05 +0000
From:      Wes Peters <wes@softweyr.com>
To:        "Auge Mike" <tobe_better@hotmail.com>, current@freebsd.org
Subject:   Re: printf....!
Message-ID:  <200302091336.05344.wes@softweyr.com>
In-Reply-To: <F93rBLSAQV6uPDVniSn0000956b@hotmail.com>
References:  <F93rBLSAQV6uPDVniSn0000956b@hotmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Saturday 08 February 2003 22:12, Auge Mike wrote:
> Hi all,
>
> I was trying to know how "printf" works in FreeBSD... I hvae reached to
> this point :
>
> #define _write(fd, s, n) \
> 	__syscall(SYS_write, (int)(fd), (const void *)(s), (size_t)(n))
>
> I'am not really familiar with the way FreeBSD handle interrupts. I like
> from any one of you to tell me what functions will be called next and in
> which files, till we get the string of the printf function argment
> displayed in the terminal.

This is the syscall (kernel entry) that implements the write(2) kernel 
function.  Then next function will be in kernel space, and will be the 
handler for SYS_write, the 'write' function in sys/kern/sys_generic.c.

By "handles interrupts" I assume you meant the syscall interface, right?

-- 

        Where am I, and what am I doing in this handbasket?

Wes Peters                                               wes@softweyr.com


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200302091336.05344.wes>