Date: | Tue, 26 Jul 2016 07:34:06 -0700 |
---|---|
From: | Xiaozhu Meng <xmeng@xxxxxxxxxxx> |
Subject: | [DynInst_API:] [dyninst/dyninst] 36bd17: Even when the jump target is unknown, we should st... |
Branch: refs/heads/master Home: https://github.com/dyninst/dyninst Commit: 36bd1735cb8ce79eaaa1be477cf6ae72cdb2b1ef https://github.com/dyninst/dyninst/commit/36bd1735cb8ce79eaaa1be477cf6ae72cdb2b1ef Author: Xiaozhu Meng <xmeng@xxxxxxxxxxx> Date: 2016-07-26 (Tue, 26 Jul 2016) Changed paths: M parseAPI/src/IA_x86.C Log Message: ----------- Even when the jump target is unknown, we should still apply tail call heuristics to check if the jump is a tail call. This can happen when the jump targets a unparsed function entry or the jump is an indirect tail call. |
[← Prev in Thread] | Current Thread | [Next in Thread→] |
---|---|---|
|
Previous by Date: | [DynInst_API:] [dyninst/dyninst] 1b9292: Started work on dataflowAPI based analysis for fin..., John Detter |
---|---|
Next by Date: | Re: [DynInst_API:] Problems in instrumenting malloc, John Detter |
Previous by Thread: | [DynInst_API:] [dyninst/dyninst] 369111: Fixed build issue in common/src/arch-x86.C, John Detter |
Next by Thread: | [DynInst_API:] [dyninst/dyninst] 372826: dataflowAPI: space out template '>>' for pre-C++11..., Josh Stone |
Indexes: | [Date] [Thread] |