From: Raymond T. <to...@rt...> - 2002-02-26 17:00:42
|
>>>>> "Sam" == Sam Steingold <sd...@gn...> writes: >> * In message <87e...@ya...> >> * On the subject of "[clisp-list] stack overflow -> into debugger?" >> * Sent on 25 Feb 2002 12:24:27 -0500 >> * Honorable Russell McManus <rus...@ya...> writes: >> >> Is there some way to get clisp to drop me into the debugger when I get >> a stack overflow condition? Sam> not really - debugger requires some stack too, and detecting an Sam> "impending" stack overflow is much more expensive than detecting an Sam> actual one. Just a thought. Have no idea if this would really work. Assume that the end of stack is unwriteable memory and that's how stack overflow is detected. Make the actual stack somewhat smaller than the allocated space, and make the extra space unwriteable. On stack overflow, make the extra space writeable so we actually have more space. Continue. When you exit the debugger, the extra stack space is made unwriteable again. If you blow the stack in the debugger, you lose. Would this work? Ray |