On Thu, Nov 10, 2005 at 08:35:25AM -0600, Lee wrote:
> Is there a way to get a stacktrace in this case so we can identify which
> execution path is causing this stack overflos ?
It could be done... Before coming up with a patch for that, what sort of
setup are you running -- filesystem, raid array, drivers, etc? Combined
with the results of a 'make checkstack' that's usually enough to get an
idea where the problem is. Thanks,
-ben
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
