search for: johnwiland

...tput to the LLVM IR first. I think you're right: I fixed my particular problem by initializing all stack variables. > I guess I could arrange for them all to be output in one fell swoop at the > start of the function. Why do you need this? I need this to make RIPE (https://github.com/johnwilander/RIPE) work. RIPE is the "runtime intrusion prevention evaluator" and it is a program that performs a lot of different attacks on itself. It relies on the order of stack variables for its stack smashing attacks. Regards, Job

I have noticed that dragonegg sometimes allocates stack objects in a different order than they were declared in the source file. I experienced this behavior when compiling RIPE (https://github.com/johnwilander/RIPE) in the function perform_attack. Unfortunately, I haven't been able to reproduce this in a minimal example. (Note that when compiling RIPE with GCC, the order of stack variables is preserved) So, I have two questions about this behavior: 1) When exactly does dragonegg reorder stack...

> I need this to make RIPE (https://github.com/johnwilander/RIPE) work. RIPE is > the "runtime intrusion prevention evaluator" and it is a program that performs > a lot of different attacks on itself. It relies on the order of stack > variables for its stack smashing attacks. Interesting, how much of other undefined / implementation-def...