I found some info on preventing attacks on the stack, so it seems to me that it should be possible to do this in a non- hostile manner.The stack overrun protection, besides not being particularily effective, will be useless for what you are trying to do. Very roughly, it places a runtime-chosen random var right before the function's return address. The function epilouge checks that the value is still there. This attempts to defeat stack overruns.
This won't work in your case because the corruption is an inherent part of your program. Utilities for stack analysis, such as the one mentioned in the bugzilla archive, or a commercial tool such as IDA pro (http://www.datarescue.com) can do it for you, if you take the bother to learn how to operate it.
Thanks,Shachar
Orna.
-- Shachar Shemesh Open Source integration consultant Home page & resume - http://www.shemesh.biz/
-------------------------------------------------------------------------- Haifa Linux Club Mailing List (http://www.haifux.org) To unsub send an empty message to [EMAIL PROTECTED]
