Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 27 Feb 2008 15:57:11 +0300
From:      Eygene Ryabinkin <rea-fbsd@codelabs.ru>
To:        "Sanjeev Kumar.S" <sanjeevfiles@yahoo.com>
Cc:        hackers@freebsd.org
Subject:   Re: synchronous freebsd print
Message-ID:  <jqsbATFLFHCJBUtaTjNU8HmtZl4@X8SeZp33V36Y2ke0Lp2TTmdKvEM>
In-Reply-To: <670902.8665.qm@web57710.mail.re3.yahoo.com>
References:  <20080227085932.GV83599@server.vk2pj.dyndns.org> <670902.8665.qm@web57710.mail.re3.yahoo.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Sanjeev,

Wed, Feb 27, 2008 at 03:00:46AM -0800, Sanjeev Kumar.S wrote:
> and Yes in the kernel code I have a "\n" at the end
> of my print, still the print is not complete and 
> the line next to it that causes the crash does
> not give the result I want. Is this a common
> scenario or am I doing something wrong.

If you're not defining PRINTF_BUFR_SIZE, then, judging by the
/sys/kern/subr_prf.c, output will be unbuffered in any case.  However,
kernel printf is not protected by locks, so it can be interrupted
by another thread, if I am correct.

May be ddb(4) will become your friend?
-- 
Eygene



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