From owner-freebsd-hackers Tue Aug 7 10:17:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ntlg.sibnet.ru (dns.sibnet.ru [217.70.96.34]) by hub.freebsd.org (Postfix) with ESMTP id 546ED37B403 for ; Tue, 7 Aug 2001 10:17:22 -0700 (PDT) (envelope-from semenu@FreeBSD.org) Received: from tlg5-ppp42.sibnet.ru (tlg5-ppp42.sibnet.ru [217.70.97.43]) by ntlg.sibnet.ru (8.9.3+Sun/8.9.3) with ESMTP id VAA06769 for ; Tue, 7 Aug 2001 21:17:15 +0400 (MSD) Date: Wed, 8 Aug 2001 00:17:13 +0600 (GMT+6) From: "Semen A. Ustimenko" X-Sender: semenu@default To: freebsd-hackers@FreeBSD.org Subject: Kernel stack size Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi! I'm developing some code running in kernel that use a lot of stack. And it seems i run into stack overflow. This results in some proc structure related parts overwrite (particulary p->p_stats->p_timer[ITIMER_PROF]) and unexpected signals. (Otherwise, it usually page faults inside swi_net_next()) Could somebody explain how this can happen (i thought i would panic and say ``stack oveflow'') and how this can be avoided? Thanks in forward! Bye! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message