Fixed cases where post-call padding not set
authorKevin Roundy <roundy@cs.wisc.edu>
Fri, 24 Sep 2010 21:46:49 +0000 (16:46 -0500)
committerKevin Roundy <roundy@cs.wisc.edu>
Fri, 24 Sep 2010 21:46:49 +0000 (16:46 -0500)
commit2876400aafdaaa1ad9150dcc8f791f497f7b6277
treee41252a49c92749d27602996f2b0ded73c5504e1
parent5108838b2c38b220ff384fb9992a5951c8f5ab32
Fixed cases where post-call padding not set

Was failing to set post-call padding jumps if our stack-analysis was inconclusive,
because we weren't instrumenting return instructions.  We also weren't padding when
parseAfterCallAndInstrument didn't result in new parsing (if the call was assumed
to be non-returning, but the subsequent instruction had been parsed anyway due to
a jump to that address).
.gitignore
dyninstAPI/src/Relocation/Atoms/CFAtom.C
dyninstAPI/src/addressSpace.C
dyninstAPI/src/hybridInstrumentation.C