Re: [DynInst_API:] API-breaking changes for upcoming Dyninst 11.0 release

[Tim Haines <thaines@xxxxxxxxxxxxxx>]

Hi, all.

Based on received feedback, the API-breaking changes listed below have been merged into the head of master. Please test your builds against this branch as soon as you can to minimize the impact of upgrading to the future 11.0 release.

Thanks.

 - Tim

---

From: Tim Haines
Sent: Monday, October 26, 2020 4:02 PM
To: dyninst-api@xxxxxxxxxxx <dyninst-api@xxxxxxxxxxx>
Subject: API-breaking changes for upcoming Dyninst 11.0 release

 

Hi, all.

We have several API-breaking changes we want to include in the next major release of Dyninst (11.0). To help everyone prepare for these changes, I've stored them on a topic branch, api_breakages, instead of merging them into master. If you could try building your software against this branch and let me know if you have any troubles (also let me know if you don't have any!), it will very much help us stay ahead of any bumps in the road we may encounter for this upcoming release. I've outlined the specific API changes below.

Many thanks.

 - Tim

P.S. Apologies if you've seen this before. I'm having troubles with the mailing list and my gmail account.

parseAPI

Removed CFGFactory::destroy_all

dyninstAPI

Removed BPatch_regExpr class

Removed "findFunctionByAddr(void *addr)". Replace with either "findFunctionByEntry" or "findFunctionsByAddr". See https://github.com/dyninst/dyninst/issues/820#issuecomment-683375892 for details.

Removed "BPatch_process::enableDumpPatchedImage"

Removed "BPatch_snippet::getCost()", "BPatch_snippet::getCostAtPoint"

patchAPI

"Patcher::create" now returns a "boost::shared_ptr<Patcher>" instead of a "Patcher*"

symtabAPI

If you have any classes which inherit from "SerializerBase" or "Serializable", those base classes should be removed. Please note that this will have no effect on the behavior of your programs as the serialization feature has been disabled since 2012.