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: 13+ 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 --
2003-09-12 17:53 stack overflow 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
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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox