I agree with going for a doc fix now and holding off on any api changes.
I think we should look seriously at the model:
- x.y.z releases only fix bugs, no functions added and none removed
- x.y releases add new functionality and add functions (but none are
deleted or renamed)
- x releases are
On 10/22/2015 01:24 PM, Bill Williams wrote:
> On 10/22/2015 03:21 PM, Josh Stone wrote:
>> On 10/22/2015 11:58 AM, Bill Williams wrote:
>>> Reorganized Monday's commits into 9.0.x (everything but the module
>>> changes) and 9.1.x (module changes only, thus far) branches. They'll
>>> both get merge
On 10/22/2015 03:21 PM, Josh Stone wrote:
On 10/22/2015 11:58 AM, Bill Williams wrote:
Reorganized Monday's commits into 9.0.x (everything but the module
changes) and 9.1.x (module changes only, thus far) branches. They'll
both get merged back to master post-releases.
Better, thanks!
There's o
On 10/22/2015 11:58 AM, Bill Williams wrote:
> Reorganized Monday's commits into 9.0.x (everything but the module
> changes) and 9.1.x (module changes only, thus far) branches. They'll
> both get merged back to master post-releases.
Better, thanks!
There's one more break that snuck into v9.0.x:
Reorganized Monday's commits into 9.0.x (everything but the module
changes) and 9.1.x (module changes only, thus far) branches. They'll
both get merged back to master post-releases.
--bw
___
Dyninst-api mailing list
Dyninst-api@cs.wisc.edu
https://lis
Dear Dyninst Developer
I have read the documents and source code of Dynisnt, and want to confirm
whether my understanding is correct.The process of the Dyninst's
instrumentation takes three steps:
(1) Recognize functions; (2) Build CFG(control flow graph) for each
"instrumentable" function; (3)
