Vadik Mironov wrote:
þÅÔ×ÅÒÇ 02 óÅÎÔÑÂÒØ 2004 22:41, Kim Woelders ÎÁÐÉÓÁÌ:
1. The allocation on the stack around 16 kilobytes is not a god idea,
because stack was invented for function calls and recursion , but not for
storing data. And this could theoretically lead to a problem in general
Vadik Mironov wrote:
Good day, everybody!
In debug mode I encounter massive stack corruption, with the help of global
call_stack array. The only reason to this is plain return in function or no
EDBUG() macro at the start of the function.
I never use the EDBUG macro stuff myself, so it may very w
Good day, everybody!
In debug mode I encounter massive stack corruption, with the help of global
call_stack array. The only reason to this is plain return in function or no
EDBUG() macro at the start of the function.
So i suggest to join DBGCHECK from events.c and EDBUG macro, here is t
Четверг 02 Сентябрь 2004 22:41, Kim Woelders написал:
> > 1. The allocation on the stack around 16 kilobytes is not a god idea,
> > because stack was invented for function calls and recursion , but not for
> > storing data. And this could theoretically lead to a problem in general
> > case, if
