[DynInst_API:] [dyninst/dyninst] 468839: In binary rewriting, when Dyninst needs to load a ...


Date: Fri, 22 Feb 2019 09:54:10 -0800
From: Xiaozhu Meng <noreply@xxxxxxxxxx>
Subject: [DynInst_API:] [dyninst/dyninst] 468839: In binary rewriting, when Dyninst needs to load a ...
  Branch: refs/heads/known_test_failures_fixes
  Home:   https://github.com/dyninst/dyninst
  Commit: 4688398b908c249e6f68657d44f198d5c2967e4c
      https://github.com/dyninst/dyninst/commit/4688398b908c249e6f68657d44f198d5c2967e4c
  Author: Xiaozhu Meng <xmeng@xxxxxxxxxxx>
  Date:   2019-02-22 (Fri, 22 Feb 2019)

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

  Log Message:
  -----------
  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.


  Commit: 027accb09e18189e7ae3d9311ce36e89a1f7de1f
      https://github.com/dyninst/dyninst/commit/027accb09e18189e7ae3d9311ce36e89a1f7de1f
  Author: Xiaozhu Meng <xmeng@xxxxxxxxxxx>
  Date:   2019-02-22 (Fri, 22 Feb 2019)

  Changed paths:
    M proccontrol/src/int_thread_db.C

  Log Message:
  -----------
  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.


Compare: https://github.com/dyninst/dyninst/compare/dce4af9c0e92...027accb09e18
[← Prev in Thread] Current Thread [Next in Thread→]
  • [DynInst_API:] [dyninst/dyninst] 468839: In binary rewriting, when Dyninst needs to load a ..., Xiaozhu Meng <=