Bongani Hlope wrote:
To enable stack unwinding for exception handling, extra exception-related
information about each function needs to be available for each stack frame.
This information describes which destructors need to be called (so that local
objects can be cleaned up), indicates whether the current function has a try
block, and lists which exceptions the associated catch clauses can handle.
Take a look at a typical OOPS trace and tell me if that will fit in a 4k stack
with C++ and stack unwinding.
C++ on Linux does not put any information on the stack for exception
handling purposes. Windows implementations do that but (a) I think the
Windows kernel has a 12K stack (b) Linux is unlikely to use the
Microsoft C++ compiler.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
-
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]
