Fixes for stackwalking and instrumentation cleanup
authorKevin Roundy <roundy@cumin.cs.wisc.edu>
Wed, 23 Jun 2010 18:17:12 +0000 (13:17 -0500)
committerKevin Roundy <roundy@cumin.cs.wisc.edu>
Wed, 23 Jun 2010 18:17:12 +0000 (13:17 -0500)
commit5dded738bf3c2aa2ae495618c7e9a6a5ac092173
treeb27bfcbf35c62b73236c2aa4a70c29241815edec
parentcca821fce38c8132257091608f95700e161017ad
Fixes for stackwalking and instrumentation cleanup

Currently, the PC values in BPatch_frames created by BPatch_thread::getCallStack API functions can correspond to relocated functions and therefore make little sense to an external user.  With this commit I'm causing these PC values to be translated to original addresses.

This commit also fixes a failure that I introduced in yesterday's commit; I had added a sanity check assert that mad incorrect assumptions about BPatch_point's instrumentation datastructures.
dyninstAPI/src/BPatch_point.C
dyninstAPI/src/BPatch_thread.C