Date: | Tue, 23 Apr 2019 07:12:34 -0700 |
---|---|
From: | Xiaozhu Meng <noreply@xxxxxxxxxx> |
Subject: | [DynInst_API:] [dyninst/dyninst] c6144a: For jump table analysis, control flow edges can be... |
Branch: refs/heads/pp_springboard Home: https://github.com/dyninst/dyninst Commit: c6144ad78965c02708e67a8d65dabb5ba9c607b6 https://github.com/dyninst/dyninst/commit/c6144ad78965c02708e67a8d65dabb5ba9c607b6 Author: Xiaozhu Meng <xmeng@xxxxxxxxxxx> Date: 2019-04-23 (Tue, 23 Apr 2019) Changed paths: M dataflowAPI/src/slicing.C Log Message: ----------- For jump table analysis, control flow edges can be created in different orders, which lead to non-deterministic slicing and non-determinisitc jump table analysis. Therefore, we need to sort source edges in slicing based on the edge's source block address and edge type to ensure deterministic slicing. |
[← Prev in Thread] | Current Thread | [Next in Thread→] |
---|---|---|
|
Previous by Date: | [DynInst_API:] [dyninst/dyninst] ffcea6: avoid infinite loop on bad DWARF CFI record, L.E.R |
---|---|
Next by Date: | [DynInst_API:] [dyninst/dyninst] 3c3393: Move architecture dependent code in PCWidget.C to ..., Xiaozhu Meng |
Previous by Thread: | [DynInst_API:] [dyninst/dyninst] c37102: Fix separate debuginfo, Sasha NÃcolas |
Next by Thread: | [DynInst_API:] [dyninst/dyninst] c6c4c0: Boost cleanup (#578), Tim Haines |
Indexes: | [Date] [Thread] |