Re: [DynInst_API:] Some documentation patches + code sample

[Bill Williams <bill@xxxxxxxxxxx>]

On 09/22/2015 05:46 PM, Alin MÃndroc wrote:

Hi,

No problem, a comment specifying the license placed at the beginning of the code would be enough?

License and that it's copyrighted by you, 2015 in a comment is sufficient.

Alin

On Sep 21, 2015 6:04 PM, "Bill Williams" <bill@xxxxxxxxxxx> wrote:

Alin--

Thanks much for the patches. I'll work out where to drop the example in and let you know.

Do you mind adding license/copyright info to your code sample? (Anything that allows us to distribute it with the manual should be fine.)

--bw

On 09/20/2015 07:11 AM, Alin MÃndroc wrote:

Hi everyone,

I have attached some code patches to the documentation, as following:

 CodeSource.tex: Added underscore in front of the names of the members of the "Hint" struct, as they are named in the source code

 Iterating.tex: Changed "findModule" to "findModuleByName"; also, quotes around "foo" came out as bogus unicode chars, so I replaced them

 LineInformation.tex: Fixed link for code sample which pointed to wrong section

 Symtab.C, Symtab.h: Added capital "O" for "getNumberofSymbols" and "getNumberofRegions", as they are named in the documentation

Also, an example that I have missed in your documentation was how to parse a file and get the assembly instructions for each function, a compilable piece of code together with build guidelines, like the sample in the manual for parseAPI which shows how to generate a CFG.

So I have also attached a code sample with this functionality, which can be built exactly like in the ParseAPI manual, section 3.1. I am not sure where to place it in the manual, so I have attached only the source code.

Regards,

Alin

_______________________________________________
Dyninst-api mailing list
Dyninst-api@xxxxxxxxxxx
https://lists.cs.wisc.edu/mailman/listinfo/dyninst-api