From: GrandMasterLee <masterlee@digitalroadkill.net>
To: Linux Geek <bourne@ToughGuy.net>
Cc: Madhavi <madhavis@sasken.com>, linux-kernel@vger.kernel.org
Subject: Re: Stack overflow
Date: 24 Jan 2003 09:32:31 -0600 [thread overview]
Message-ID: <1043422351.17256.1.camel@localhost> (raw)
In-Reply-To: <3E30F0FC.1010008@ToughGuy.net>
On Fri, 2003-01-24 at 01:53, Linux Geek wrote:
> >
> >
> >I have a functionality which works well if the code whcih performs this
> >function is embedded in the required function. If this functionality is
> >implemented as a separate function, and this function is called at the
> >required place, the system crashes. I have used KDB for debugging. But,
> >
> >
> I'd suggest check the args passed to the function and the sizes they
> would consume when they are passed as 'call by value'.
> Try to pass them as pointers maybe.
>
> Yes, i think there is a limit on kernel stack but not i'm not too sure
> about the number.
The kernel has an 8K stack max. That said, it *could* be your stack. Do
you get any panics or oops? If so, you *could* write them down :-D And
debug them later. If it appears corrupted, then it's probably stack.
next prev parent reply other threads:[~2003-01-24 15:24 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-24 7:08 Stack overflow Madhavi
2003-01-24 7:53 ` Linux Geek
2003-01-24 15:32 ` GrandMasterLee [this message]
2003-01-24 15:41 ` Madhavi
2003-01-24 16:42 ` Richard B. Johnson
2003-01-24 16:52 ` Gianni Tedesco
-- strict thread matches above, loose matches on Subject: below --
2004-03-22 17:40 stack overflow Stuart_Hayes-DYMqY+WieiM
2004-03-10 17:08 Stuart_Hayes-DYMqY+WieiM
[not found] ` <CE41BFEF2481C246A8DE0D2B4DBACF4F020E5FD9-novRXWwkcpil7xnNSM18fRtLTTO9Z+wMojBamW5iJbs@public.gmane.org>
2004-03-10 18:40 ` Len Brown
2004-03-10 15:56 Stuart_Hayes-DYMqY+WieiM
2004-03-09 22:48 Moore, Robert
2004-03-09 21:04 Stuart_Hayes-DYMqY+WieiM
2004-03-09 20:00 Stuart_Hayes-DYMqY+WieiM
2004-03-09 18:34 Moore, Robert
2004-03-08 16:43 Stuart_Hayes-DYMqY+WieiM
[not found] ` <CE41BFEF2481C246A8DE0D2B4DBACF4F128AA4-novRXWwkcpil7xnNSM18fRtLTTO9Z+wMojBamW5iJbs@public.gmane.org>
2004-03-08 18:26 ` Andi Kleen
[not found] ` <20040308182630.GB9490-B4tOwbsTzaBolqkO4TVVkw@public.gmane.org>
2004-03-09 7:17 ` Len Brown
2004-03-10 4:33 ` Len Brown
[not found] ` <1078893223.2346.585.camel-D2Zvc0uNKG8@public.gmane.org>
2004-03-10 13:32 ` Andi Kleen
[not found] ` <20040310133208.GC12272-B4tOwbsTzaBolqkO4TVVkw@public.gmane.org>
2004-03-10 18:44 ` Len Brown
2003-09-12 17:53 Breno
2003-09-12 22:50 ` Andreas Dilger
2003-09-12 19:14 ` Breno
2003-09-12 23:06 ` William Lee Irwin III
2003-09-12 19:23 ` Breno
2003-09-12 23:18 ` Alan Cox
2003-09-12 23:25 ` William Lee Irwin III
2000-09-06 13:25 Zeshan Ahmad
2000-09-05 19:03 Zeshan Ahmad
2000-09-06 8:33 ` Mark Hemment
2000-09-04 10:47 Zeshan Ahmad
2000-09-04 11:03 ` Matti Aarnio
2000-09-04 11:23 ` Tigran Aivazian
2000-09-05 10:55 ` Mark Hemment
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=1043422351.17256.1.camel@localhost \
--to=masterlee@digitalroadkill.net \
--cc=bourne@ToughGuy.net \
--cc=linux-kernel@vger.kernel.org \
--cc=madhavis@sasken.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.