[DynInst_API:] [dyninst/dyninst] 2a4bbf: Attempts to fix legacy test failures in Dyninst te...


Date: Wed, 06 Mar 2019 16:08:23 -0800
From: Xiaozhu Meng <noreply@xxxxxxxxxx>
Subject: [DynInst_API:] [dyninst/dyninst] 2a4bbf: Attempts to fix legacy test failures in Dyninst te...
  Branch: refs/heads/master
  Home:   https://github.com/dyninst/dyninst
  Commit: 2a4bbf763c87a0a6168de2630cf74ba821e6472f
      https://github.com/dyninst/dyninst/commit/2a4bbf763c87a0a6168de2630cf74ba821e6472f
  Author: Xiaozhu Meng <mxz297@xxxxxxxxx>
  Date:   2019-03-06 (Wed, 06 Mar 2019)

  Changed paths:
    M dyninstAPI/h/BPatch_binaryEdit.h
    M dyninstAPI/src/BPatch_binaryEdit.C
    M proccontrol/src/int_thread_db.C

  Log Message:
  -----------
  Attempts to fix legacy test failures in Dyninst test suite (#549)

* In binary rewriting, when Dyninst needs to load a library,
    it does not check whether this library has been loaded before or not.
    Dyninst will create multiple binaryEdit objects for one library, which can cause inconsistent states between these objects.

    This fix adds a map to BPatch_binaryEdit to make sure each library is only loaded once.

* Fix pc_tls failures in dyamically linked binaries.
    The root cause is a broken library name matching code.
    Just should boost:filesystem::path to deal with file paths.

Closes #549


[← Prev in Thread] Current Thread [Next in Thread→]
  • [DynInst_API:] [dyninst/dyninst] 2a4bbf: Attempts to fix legacy test failures in Dyninst te..., Xiaozhu Meng <=