| |||||||||||||
4K stacks: some issues remain4K stacks: some issues remainPosted May 22, 2004 19:54 UTC (Sat) by giraffedata (subscriber, #1954)In reply to: 4K stacks: some issues remain by dac Parent article: 4K stacks: some issues remain Since you've apparently decoded the program, could you post a description of what it does? I don't mean a character-by-character description of its operation; just the basic strategy for finding stack overflowing code.
(Log in to post comments)
4K stacks: some issues remain Posted May 22, 2004 20:32 UTC (Sat) by dac (subscriber, #9260) [Link] see the full post in:http://lkml.org/lkml/2004/5/14/34 It has comments!
4K stacks: some issues remain Posted May 25, 2004 22:57 UTC (Tue) by jzbiciak (✭ supporter ✭, #5246) [Link] Looks to me like it's grepping through a disassembly for subtract instructions that move the stack pointer down, and pulling out the subtraction constant. This is useful because I'm pretty sure GCC moves the stack pointer in one go rather than incrementally through the life of the function.By doing this, you can determine the stack footprint of most functions pretty quickly, and focus your attention on the heavy users.
|
|||||||||||||