Re: [DynInst_API:] REX prefix

Hi Victor, Bill is out this week. So I will try to look into this problem. I am now able to reproduce the problem and identify the buggy code. I will send you a patch when I have a fix. Thanks --Xiaozhu On Mon, Jun 8, 2015 at 11:25 AM, Victor van der Veen vvdv...@gmail.com wrote: Hello,

Re: [DynInst_API:] writeFile fails

On Fri, Jun 12, 2015 at 11:34 AM, Essa Alkuwari q...@0x80.org wrote: I'm trying to deal with static linked binaries. I openBinary then insert some snippets in a function. Everything looks fine until I try to writeFile which takes me to here :

Re: [DynInst_API:] Patching every basic block of a given elf binary

Hi Shuai, BPatch_entry represents the entry of a function. You should use BPatch_locBasicBlockEntry instead of BPatch_entry. Or, you can try BPatch_point* BPatch_basicBlock::findEntryPoint(). Thanks --Xiaozhu On Sat, Aug 22, 2015 at 9:06 PM, Shuai Wang wangshuai...@gmail.com wrote: Dear

Re: [DynInst_API:] [PATCH 2/2] common: try process_vm_readv/writev for Linux bulk access

This patch is applied, tested and pushed. On Mon, Aug 3, 2015 at 9:34 AM, Josh Stone jist...@redhat.com wrote: On 08/03/2015 09:25 AM, Xiaozhu Meng wrote: Hi Josh, Could you send me this patch in a patch file so that I can directly apply? I will run this patch on batlab to make sure it does

Re: [DynInst_API:] getLoopHead interface in BPatch_basicBlockLoop class

-getLoopBasicBlocks(blocks); for (unsigned int i = 0; i blocks.size(); ++i) { BPatch_basicBlock* block = blocks[i]; Or is it more complicated than that? Thanks, Jim G Thanks, Jim G On 07/28/2015 10:37 AM, Xiaozhu Meng wrote: Hi Jim

Re: [DynInst_API:] getLoopHead interface in BPatch_basicBlockLoop class

BPatch_VectorBPatch_basicBlock* blocks; 150loop-getLoopBasicBlocks(blocks); 151 152for (unsigned int i = 0; i blocks.size(); ++i) 153{ ... ... Thanks, Jim G On 09/23/2014 04:57 PM, Xiaozhu Meng wrote: Hi, We are planing

[DynInst_API:] COMMIT: fix ParseAPI build on non-x86 platforms

Analyzing stripped binaries is currently only enabled on x86 and x86-64 platforms. On other platforms, code specific to x86 or x86-64 should not be compiled. ___ Dyninst-api mailing list Dyninst-api@cs.wisc.edu

[DynInst_API:] COMMIT: more manual updates

1. Update const qualifier for return values of some ParseAPI interfaces such as CodeObject::funcs(). 2. Update LoopTreeNode namings ___ Dyninst-api mailing list Dyninst-api@cs.wisc.edu https://lists.cs.wisc.edu/mailman/listinfo/dyninst-api

Re: [DynInst_API:] dyninst help

Hi, It seems to me that you should use a different way to get function call instrumentation points. I would recommend that you first get the set of functions that you are interested; then for each function, you can get all the call site instrumentation points. So I guess you want code like:

[DynInst_API:] COMMIT: windows build fix and parseAPI manual

This commit fixes windows build failure caused by my warning suppression and also finishes parseAPI manual consistency check against the header files. ___ Dyninst-api mailing list Dyninst-api@cs.wisc.edu

[DynInst_API:] COMMIT: Merge changes in parsing

This commit merges my various changes in parsing to master, including machine learning based gap parsing, new jump table analysis and fixes to our existing tail call heuristics. It also includes changes made to slicing code to support the new jump table analysis, where users now have a better

Re: [DynInst_API:] commit: further 9.1 fixes

On Tue, Dec 8, 2015 at 1:26 PM, Bill Williams wrote: > On 12/08/2015 12:47 PM, Barton Miller wrote: > >> How often are these indirect vs. direct? Does it ever happen that the >> indirect points to static tables of addresses, so is statically resolvable? >> >> Mostly they're

Re: [DynInst_API:] Abort on Xeon hosted dyninst running through Intel MIC application

Hi Jim, I believe I happened to fix this bug yesterday. I downloaded your binary and parsing it finished cleanly. I attach my patch and please apply the patch to dataflowAPI/src/slicing.C. Let me know if it works or not. Thanks, --Xiaozhu On Thu, Dec 3, 2015 at 11:25 AM, Jim Galarowicz

[DynInst_API:] [dyninst/dyninst] da7c75: DataflowAPI manual writing

Branch: refs/heads/VEX Home: https://github.com/dyninst/dyninst Commit: da7c751193bb289450d25de91d51fe13ace09563 https://github.com/dyninst/dyninst/commit/da7c751193bb289450d25de91d51fe13ace09563 Author: Xiaozhu Meng <xm...@cs.wisc.edu> Date: 2016-06-03 (Fri, 03 Ju

[DynInst_API:] [dyninst/dyninst] eedef3: Various fixes for jump table analysis 1. add instr...

Branch: refs/heads/VEX Home: https://github.com/dyninst/dyninst Commit: eedef36d46ae5a21c0f189ad2d9393b8391ef2b1 https://github.com/dyninst/dyninst/commit/eedef36d46ae5a21c0f189ad2d9393b8391ef2b1 Author: Xiaozhu Meng <xm...@cs.wisc.edu> Date: 2016-06-10 (Fri, 10 Ju

[DynInst_API:] [dyninst/dyninst] f09e07: Simplify v + v * c = v * (c + 1), where v is a var...

Branch: refs/heads/VEX Home: https://github.com/dyninst/dyninst Commit: f09e071fd361969619896e7155c8f3e7fb57de11 https://github.com/dyninst/dyninst/commit/f09e071fd361969619896e7155c8f3e7fb57de11 Author: Xiaozhu Meng <xm...@cs.wisc.edu> Date: 2016-06-14 (Tue, 14 Ju

[DynInst_API:] [dyninst/dyninst] eedef3: Various fixes for jump table analysis 1. add instr...

Branch: refs/heads/master Home: https://github.com/dyninst/dyninst Commit: eedef36d46ae5a21c0f189ad2d9393b8391ef2b1 https://github.com/dyninst/dyninst/commit/eedef36d46ae5a21c0f189ad2d9393b8391ef2b1 Author: Xiaozhu Meng <xm...@cs.wisc.edu> Date: 2016-06-10 (Fri, 10 Ju

Re: [DynInst_API:] oneTimeCode in an exit callback not working

Hi, I ran the example on a RHEL7 machine. From the debugging log of Dyninst, I saw that the one time code in the exit callback was successfully executed, with a return value "0". In the case of calling "puts", I guess the stdout has been closed before the exit callback. But I have not been able

[DynInst_API:] [dyninst/dyninst] 8f85a8: Indirect tail calls can be PC-relative and should ...

Branch: refs/heads/master Home: https://github.com/dyninst/dyninst Commit: 8f85a86caa63d595cddf9a4cc4d8e2695b983bdc https://github.com/dyninst/dyninst/commit/8f85a86caa63d595cddf9a4cc4d8e2695b983bdc Author: Xiaozhu Meng <xm...@cs.wisc.edu> Date: 2016-07-28 (Thu, 28 Ju

[DynInst_API:] [dyninst/dyninst] 8e4f98: Massive dataflowAPI manual writing

Branch: refs/heads/v9.2.x Home: https://github.com/dyninst/dyninst Commit: 8e4f980a45b45f15b8f704ad166110ec4483b0cc https://github.com/dyninst/dyninst/commit/8e4f980a45b45f15b8f704ad166110ec4483b0cc Author: Xiaozhu Meng <xm...@cs.wisc.edu> Date: 2016-05-24 (Tue, 24 Ma

[DynInst_API:] [dyninst/dyninst] 36bd17: Even when the jump target is unknown, we should st...

Branch: refs/heads/master Home: https://github.com/dyninst/dyninst Commit: 36bd1735cb8ce79eaaa1be477cf6ae72cdb2b1ef https://github.com/dyninst/dyninst/commit/36bd1735cb8ce79eaaa1be477cf6ae72cdb2b1ef Author: Xiaozhu Meng <xm...@cs.wisc.edu> Date: 2016-07-26 (Tue, 26 Ju

[DynInst_API:] [dyninst/dyninst] f51f18: When reaching shared blocks that have been parsed, ...

Branch: refs/heads/v9.2_patches Home: https://github.com/dyninst/dyninst Commit: f51f18a3aa7ffda005e55b87045ac5fcee9f43f4 https://github.com/dyninst/dyninst/commit/f51f18a3aa7ffda005e55b87045ac5fcee9f43f4 Author: Xiaozhu Meng <xm...@cs.wisc.edu> Date: 2016-07-12 (Tue,

[DynInst_API:] [dyninst/dyninst] a75840: Bump version number and date for dyninstAPI and pr...

Branch: refs/heads/master Home: https://github.com/dyninst/dyninst Commit: a7584082c4a600deb1bea956c6f0c8917f690d98 https://github.com/dyninst/dyninst/commit/a7584082c4a600deb1bea956c6f0c8917f690d98 Author: Xiaozhu Meng <xm...@cs.wisc.edu> Date: 2016-06-29 (Wed, 29 Ju

[DynInst_API:] [dyninst/dyninst] 73c3bb: A memory access to a known address should be consi...

Branch: refs/heads/meng/lulesh-fix Home: https://github.com/dyninst/dyninst Commit: 73c3bb0999f0e5afe44bc70d0fbb16ea9d42b3dc https://github.com/dyninst/dyninst/commit/73c3bb0999f0e5afe44bc70d0fbb16ea9d42b3dc Author: Xiaozhu Meng <xm...@cs.wisc.edu> Date: 2017-02-23 (T

[DynInst_API:] [dyninst/dyninst] bdc29b: Allow reading of operands with a SgAsmBinaryLsr as...

commit/5bbe517aaa7e0f0fcae61d4a5e88f5e25ed7dcd0 Author: Xiaozhu Meng <xm...@cs.wisc.edu> Date: 2016-11-04 (Fri, 04 Nov 2016) Changed paths: M dataflowAPI/rose/semantics/DispatcherARM64.C M dataflowAPI/rose/semantics/DispatcherARM64.h M instructionAPI/src/InstructionDecoder-aarc

[DynInst_API:] [dyninst/dyninst] 6816ca: Add description for BPatch::registerDynamicCallCal...

Branch: refs/heads/release9.3/fixes/dyninstAPI_manual Home: https://github.com/dyninst/dyninst Commit: 6816ca3bf7e84684445c6cfc308d1e591f75374a https://github.com/dyninst/dyninst/commit/6816ca3bf7e84684445c6cfc308d1e591f75374a Author: Xiaozhu Meng <xm...@cs.wisc.edu>

Re: [DynInst_API:] --SERIOUS-- #109: Module does not exist writeFile failed

Hi, Is it possible to send me your mutator and mutatee? I can try to see what is going on. Thanks, --Xiaozhu On Wed, Jan 4, 2017 at 11:14 AM, Duke Dude wrote: > Hi, > > > I've installed the dyinst 9.3 on Kali (debian based) and running the > example provided in

[DynInst_API:] [dyninst/dyninst] 9853dc: Line table can exists, but does not contain any en...

Branch: refs/heads/release9.3/fixes/icc_binaries Home: https://github.com/dyninst/dyninst Commit: 9853dc470c5974e47276ec9d359fe0f542b3f663 https://github.com/dyninst/dyninst/commit/9853dc470c5974e47276ec9d359fe0f542b3f663 Author: Xiaozhu Meng <xm...@cs.wisc.edu> Date: 2

Re: [DynInst_API:] Static Taint Analysis using Dyninst

Hi Sazzadur, It is suspicious that the absloc in your case was reported as a heap variable. It is clearly a stack variable. When the absloc is classified as a heap variable, slicing will have difficult time to match it with other heap variables statically because we do no necessarily know the

Re: [DynInst_API:] Static Taint Analysis using Dyninst

Hi Sazzadur, Let me explain what's happening. >> >> *ac.convert(insn, b->start(), f, b, assignments);* >> > The above line of code is causing us the problem. The second parameter of convert should be the address of the instruction you want to convert. In your code, you always provide the

Re: [DynInst_API:] Static Taint Analysis using Dyninst

> > > * cout << (out.type() == Absloc::Unknown) << endl;* > In the above line, out is in type of class AbsRegion, which represents one or multiple abstract locations. When we know a AbsRegion represents a definite abstract location, its type is set to be unknown (I know this is a little bit

Re: [DynInst_API:] Dyninst Issue with C++11 chrono

Hi Zongyao, I am sorry for the late response. I downloaded your code but I was not able to reproduce your error. I compiled your mutator and mutatees, and the rewritten chrono mutatee executed normally without any segment fault. I am using a fresh clone of the master branch on Github. Which

Re: [DynInst_API:] where to find the code for handling switch() statements?

Hi Thomas, I am working with an improved jump table analysis. Its prototype is available at my Dyninst fork ( https://github.com/mxz297/dyninst/tree/jump_table_multi_slices). This improved version should be merged back to mainstream Dyninst in the near future. Could you try my version to see

[DynInst_API:] [dyninst/dyninst] f9c8c7: Fix uninitialized return value in line info

Branch: refs/heads/v9.3.x Home: https://github.com/dyninst/dyninst Commit: f9c8c70c0a808beed50cb2cc4284922d82e7363f https://github.com/dyninst/dyninst/commit/f9c8c70c0a808beed50cb2cc4284922d82e7363f Author: Xiaozhu Meng <xm...@cs.wisc.edu> Date: 2017-08-29 (Tue, 29 Au

Re: [DynInst_API:] Question on potential memory leaks

Hi Thomas, I had some memory issues related to ROSE in Dyninst, but they were not about memory leaks. My experiences are that ROSE internally has their own memory management system, including their customized small object allocation, deallocation, and their own implementation for shared pointers.

Re: [DynInst_API:] where to find the code for handling switch() statements?

gt;>> 14000h)[rcx+rax*4] >>> .text:00014004D9EC add rax, rcx >>> .text:00014004D9EF jmp rax ; switch >>> jump >>> .text:00014004D9F1 ; -- >>> --

Re: [DynInst_API:] Indirect Control Flow Target Deduction in CFG

n the form of executable examples. I > find it bit hard to piece together whole working code from the snippets in > the documentation at some places. > > Thanks > Buddhika > > > On Mon, Nov 13, 2017 at 9:37 AM, Xiaozhu Meng <mxz...@gmail.com> wrote: > >> Hi Bu

Re: [DynInst_API:] Control Flow Graph example with parseAPI

__ >> From: Dyninst-api <dyninst-api-boun...@cs.wisc.edu> on behalf of Thomas >> Dullien <thomasdull...@google.com> >> Sent: Monday, December 4, 2017 4:24 AM >> To: Buddhika Chamith Kahawitage Don >> Cc: Xiaozhu Meng; dyninst-api >>

Re: [DynInst_API:] Control Flow Graph example with parseAPI

Hi Buddhika, I have not encountered such issue before. If you still have this problem, you can send me you source file and ELF binary, and I will try to reproduce your issue and see what is happening. Thanks, --Xiaozhu On Fri, Nov 10, 2017 at 7:08 PM, Buddhika Chamith Kahawitage Don <

Re: [DynInst_API:] Indirect Control Flow Target Deduction in CFG

Hi Buddhika, I am sorry for the late response. In terms of how ParseAPI handle indirect control flows, ParseAPI will try to resolve indirect jumps and if these indirect jumps correspond to a switch statement in the source code, ParseAPI typically can finds the indirect jump targets. You can get

[DynInst_API:] [dyninst/dyninst] 27b0a9: 1. Fix codegen for ADR instructions

Branch: refs/heads/arm64/feature/relocation Home: https://github.com/dyninst/dyninst Commit: 27b0a9197b1be530bfd3e98e72ccd24510aae9a4 https://github.com/dyninst/dyninst/commit/27b0a9197b1be530bfd3e98e72ccd24510aae9a4 Author: Xiaozhu Meng <xm...@cs.wisc.edu> Date: 2017

[DynInst_API:] [dyninst/dyninst] f7957c: Take the fix for the memory issue in dwarf parsing...

Branch: refs/heads/master Home: https://github.com/dyninst/dyninst Commit: f7957cc3e9e9436929ec332667b7aa42a7c08e60 https://github.com/dyninst/dyninst/commit/f7957cc3e9e9436929ec332667b7aa42a7c08e60 Author: Xiaozhu Meng <xm...@cs.wisc.edu> Date: 2017-10-12 (Thu, 12 Oc

[DynInst_API:] [dyninst/dyninst] aa0b62: don't skip the first line in all but first range.

fWalker.C Log Message: --- Merge pull request #403 from dyninst/sasha/fix-dwarf-symbol-frame fix dwarf symbol frame Commit: f7957cc3e9e9436929ec332667b7aa42a7c08e60 https://github.com/dyninst/dyninst/commit/f7957cc3e9e9436929ec332667b7aa42a7c08e60 Author: Xiaozhu Meng <xm...@

Re: [DynInst_API:] FATAL 68 Dyninst

gt;> code that is failing? I believe that should be the one because the error >>> message I am getting apparently comes from the *setenvPreload *function, >>> but I am not 100% sure, >>> >>> At first, I tried to install the current master branch but I got

Re: [DynInst_API:] Dyninst::ParseAPI::SymtabCodeSource::init_try_blocks(): Assertion `!"WARNING: overlapping try blocks\n"' failed.

Hi Jim, In theory, try blocks should not overlap because otherwise how we know which catch block to handle the exception happened at the overlapping address. So, it is more likely that there is a problem with the eh_frame parsing, which leads to wrong try block ranges. For debugging, can you

[DynInst_API:] [dyninst/dyninst] c4914b: 1. Add more non-returning functions

Branch: refs/heads/new-parallel-parsing Home: https://github.com/dyninst/dyninst Commit: c4914b9d149c61b0405028d797b5653381a66b87 https://github.com/dyninst/dyninst/commit/c4914b9d149c61b0405028d797b5653381a66b87 Author: Xiaozhu Meng <xm...@cs.wisc.edu> Date: 2018-05-0

Re: [DynInst_API:] Status of Dyninst 10

Hi, Dyninst 10 is going to be released before July. The current master branch on the github is close to Dyninst 10 in terms of API. One of the remaining task before releasing Dyninst 10 is integrating parallel parsing. The main interface change caused by this task is changing

[DynInst_API:] [dyninst/dyninst] e86e0f: Add FORCE_BOOST CMake option for @lee218llnl

eInformation.C M symtabAPI/src/Object-elf.C M symtabAPI/src/Symtab.C Log Message: --- Merge commit 'd0160a8' into v9.3.x Commit: f9c8c70c0a808beed50cb2cc4284922d82e7363f https://github.com/dyninst/dyninst/commit/f9c8c70c0a808beed50cb2cc4284922d82e7363f Author: X

[DynInst_API:] [dyninst/dyninst] 2c1506: For ARMv8 stack walking,

Branch: refs/heads/arm64-cray-fixes Home: https://github.com/dyninst/dyninst Commit: 2c1506932c67c819f3ab119939b4d24f788044fd https://github.com/dyninst/dyninst/commit/2c1506932c67c819f3ab119939b4d24f788044fd Author: Xiaozhu Meng <xm...@cs.wisc.edu> Date: 2018-05-21 (M

[DynInst_API:] [dyninst/dyninst] 93cc79: 1. If finalizing a function needs to invoke a pars...

Branch: refs/heads/new-parallel-parsing Home: https://github.com/dyninst/dyninst Commit: 93cc790a61d2f8c91ba2c7a7d6b63695e7027daf https://github.com/dyninst/dyninst/commit/93cc790a61d2f8c91ba2c7a7d6b63695e7027daf Author: Xiaozhu Meng <xm...@cs.wisc.edu> Date: 2018-05-1

[DynInst_API:] [dyninst/dyninst] 67fce2: Revisit locking for parallel parsing

Branch: refs/heads/new-parallel-parsing Home: https://github.com/dyninst/dyninst Commit: 67fce2e5d95c1e999e94e82765a334eaab6ef4a2 https://github.com/dyninst/dyninst/commit/67fce2e5d95c1e999e94e82765a334eaab6ef4a2 Author: Xiaozhu Meng Date: 2018-06-11 (Mon, 11 Jun 2018

Re: [DynInst_API:] OPENMP Support with Dyninst

Hi Jordi, I am sorry for the late response. Based on my 7-year experience working in the Dyninst group, I am not aware of any thread of work following up the OpenMP Support document. My best guess is that it was a research project, but never made into the mainstream Dyninst. Thanks, --Xiaozhu

Re: [DynInst_API:] Creating ParseAPI graphs to CFGs for externalrepresentations; adding line map information from external sources

; > // iterate blocks > > // add blocks > > // iterate targets > > // add edges > > } > > > > Regards, > > Keren > > > > Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for > Windows 10 > > > >

[DynInst_API:] [dyninst/dyninst] 3385cd: 1. Do not make testsuite a requirement for install...

Branch: refs/heads/new-parallel-parsing Home: https://github.com/dyninst/dyninst Commit: 3385cd6c252270ad7c92dc5550e149a3b0c1566f https://github.com/dyninst/dyninst/commit/3385cd6c252270ad7c92dc5550e149a3b0c1566f Author: Xiaozhu Meng Date: 2018-06-19 (Tue, 19 Jun 2018

[DynInst_API:] [dyninst/dyninst] 9f497d: Change function return status to std::atomic to av...

Branch: refs/heads/new-parallel-parsing Home: https://github.com/dyninst/dyninst Commit: 9f497d9590bfef991005b57c4ef971b7314d5bed https://github.com/dyninst/dyninst/commit/9f497d9590bfef991005b57c4ef971b7314d5bed Author: Xiaozhu Meng Date: 2018-05-29 (Tue, 29 May 2018

[DynInst_API:] [dyninst/dyninst] 8b07f6: Merge branch 'v9.3.x'

https://github.com/dyninst/dyninst/commit/f7957cc3e9e9436929ec332667b7aa42a7c08e60 Author: Xiaozhu Meng Date: 2017-10-12 (Thu, 12 Oct 2017) Changed paths: M symtabAPI/src/dwarfWalker.C M symtabAPI/src/dwarfWalker.h Log Message: --- Take the fix for the memory issue

[DynInst_API:] [dyninst/dyninst] 501603: std::once_flag should not be declared as local var...

Branch: refs/heads/new-parallel-parsing Home: https://github.com/dyninst/dyninst Commit: 5016030458c1def8587d06d1324cea6e1c65e3ba https://github.com/dyninst/dyninst/commit/5016030458c1def8587d06d1324cea6e1c65e3ba Author: Xiaozhu Meng Date: 2018-05-29 (Tue, 29 May 2018

Re: [DynInst_API:] Creating ParseAPI graphs to CFGs for external representations; adding line map information from external sources

Hi John, I can answer the part about ParseAPI. You can definitely use the CFGFactory to construct your ParseAPI CFG, which should contains a bunch of ParseAPI::Function, ParseAPI::Block, and ParseAPI::Edge objects. Then, you can invoke loop analysis through Function objects. You won't have the

Re: [DynInst_API:] Report an assertion with the latest git version of Dyninst

Hi Jim, Please send us the binary for debugging. Sasha: the assertion happens in parsing for try/catch blocks. I guess this can be related to your recent fixes for parsing try/catch blocks. Please take a look at this issue. Thanks, --Xiaozhu On Fri, Jun 29, 2018 at 10:17 AM Jim Galarowicz

[DynInst_API:] [dyninst/dyninst] a6a661: The previous fix should only be compiled on arm

Branch: refs/heads/arm64-cray-fixes Home: https://github.com/dyninst/dyninst Commit: a6a661c980daab4c6e22a9c6e9b3d7a6659457a2 https://github.com/dyninst/dyninst/commit/a6a661c980daab4c6e22a9c6e9b3d7a6659457a2 Author: Xiaozhu Meng Date: 2018-06-27 (Wed, 27 Jun 2018) Changed

[DynInst_API:] [dyninst/dyninst] 07ebc3: 1. A function that does a system may not save x30 ...

Branch: refs/heads/arm64-cray-fixes Home: https://github.com/dyninst/dyninst Commit: 07ebc3a73d0c5fb3f9f6b4163dc57043008453c6 https://github.com/dyninst/dyninst/commit/07ebc3a73d0c5fb3f9f6b4163dc57043008453c6 Author: Xiaozhu Meng Date: 2018-06-22 (Fri, 22 Jun 2018) Changed

[DynInst_API:] [dyninst/dyninst] 86fbb5: 1. IFUNC is real code

Branch: refs/heads/new-parallel-parsing Home: https://github.com/dyninst/dyninst Commit: 86fbb589e2dc5163364738c552bbb2bb568a3b1a https://github.com/dyninst/dyninst/commit/86fbb589e2dc5163364738c552bbb2bb568a3b1a Author: Xiaozhu Meng Date: 2018-06-20 (Wed, 20 Jun 2018

Re: [DynInst_API:] FATAL 68 Dyninst

deCoverage *example where it said that couldn't find it so, I > decided to use your tagged versions instead and that problem did not appear > to me again, > > Thanks > > Alberto Olmo. > > > 2018-04-26 15:29 GMT+02:00 Xiaozhu Meng <xm...@cs.wisc.edu>: > >> Hi Alberto

Re: [DynInst_API:] Ignore certain signals

gnals at run-time, and I > don't want to pay for the extra ptrace/Dyninst overhead. This might be a > ptrace limitation, and simply not possible though. > > Best, > Vitor > > On 1 May 2018 at 16:15, Xiaozhu Meng <mxz...@gmail.com> wrote: > >> Hi Victor, >> >

Re: [DynInst_API:] Ignore certain signals

Hi Victor, Can you profile what signals are causing the slowdown? Dyninst uses a few different signals such as SIGSTOP, SIGTRAP, SIGUSR1, and SIGUSR2, for different purposes. Depending on which signal or signals are causing the problem, we may be able to figure out a way to let Dyninst not act on

[DynInst_API:] [dyninst/dyninst] 45feff: Add unstrip and codeCoverage to the example dir. W...

Branch: refs/heads/master Home: https://github.com/dyninst/dyninst Commit: 45feff81435754b317f980e33a9bad7de4846de5 https://github.com/dyninst/dyninst/commit/45feff81435754b317f980e33a9bad7de4846de5 Author: Xiaozhu Meng <xm...@cs.wisc.edu> Date: 2017-12-29 (Fri, 29 De

[DynInst_API:] [dyninst/dyninst] bd74a8: Clean unwanted files

Branch: refs/heads/master Home: https://github.com/dyninst/dyninst Commit: bd74a859301f32ee8b24930e19bf07e4b07e2bb2 https://github.com/dyninst/dyninst/commit/bd74a859301f32ee8b24930e19bf07e4b07e2bb2 Author: Xiaozhu Meng <xm...@cs.wisc.edu> Date: 2017-12-29 (Fri, 29 De

[DynInst_API:] [dyninst/dyninst] 0dbfa3: Should only check for thunk call when it is a call...

Branch: refs/heads/master Home: https://github.com/dyninst/dyninst Commit: 0dbfa36c9cc535f4dd25e657f0e1d2b54df29710 https://github.com/dyninst/dyninst/commit/0dbfa36c9cc535f4dd25e657f0e1d2b54df29710 Author: Xiaozhu Meng <xm...@cs.wisc.edu> Date: 2018-01-12 (Fri, 12 Ja

[DynInst_API:] [dyninst/dyninst] 0ee916: ParseAPI should treat IFUNC type symbols as code

Branch: refs/heads/master Home: https://github.com/dyninst/dyninst Commit: 0ee9160fbc22ba6f871f4f03130bdbe4ae2d40a7 https://github.com/dyninst/dyninst/commit/0ee9160fbc22ba6f871f4f03130bdbe4ae2d40a7 Author: Xiaozhu Meng <xm...@cs.wisc.edu> Date: 2018-01-11 (Thu, 11 Ja

Re: [DynInst_API:] inconsistent handling for non-returning functions

Hi John, I am able to reproduce the problem and will start to investigate it. I will let you know when I fix it. Thanks, --Xiaozhu On Wed, Feb 14, 2018 at 12:50 PM, John Mellor-Crummey wrote: > Non-returning functions and calls to them are not being processed properly > by

[DynInst_API:] [dyninst/dyninst] a89e8c: 1. Replace std::atomic with boost::atomic so that ...

Branch: refs/heads/new-parallel-parsing Home: https://github.com/dyninst/dyninst Commit: a89e8c9d74f0f5582389f6446aecfed5d99a2162 https://github.com/dyninst/dyninst/commit/a89e8c9d74f0f5582389f6446aecfed5d99a2162 Author: Xiaozhu Meng Date: 2018-07-30 (Mon, 30 Jul 2018

[DynInst_API:] [dyninst/dyninst] 1e30a1: Fix undeterministic tail call identification resul...

Branch: refs/heads/new-parallel-parsing Home: https://github.com/dyninst/dyninst Commit: 1e30a1200d2aef0b46b048088d99a7dd99ff5675 https://github.com/dyninst/dyninst/commit/1e30a1200d2aef0b46b048088d99a7dd99ff5675 Author: Xiaozhu Meng Date: 2018-08-05 (Sun, 05 Aug 2018

[DynInst_API:] [dyninst/dyninst] 21c93a: Should not trigger finalizing during slicing

Branch: refs/heads/new-parallel-parsing Home: https://github.com/dyninst/dyninst Commit: 21c93abcd5fd918c78354a9ae960e2d4310baa91 https://github.com/dyninst/dyninst/commit/21c93abcd5fd918c78354a9ae960e2d4310baa91 Author: Xiaozhu Meng Date: 2018-08-14 (Tue, 14 Aug 2018

[DynInst_API:] [dyninst/dyninst] 0dc630: The register map should also be in TLS

Branch: refs/heads/new-parallel-parsing Home: https://github.com/dyninst/dyninst Commit: 0dc63035bdeaa71f896cdda09e8659cc8155e9ae https://github.com/dyninst/dyninst/commit/0dc63035bdeaa71f896cdda09e8659cc8155e9ae Author: Xiaozhu Meng Date: 2018-08-06 (Mon, 06 Aug 2018

Re: [DynInst_API:] Status of Dyninst 10

version or the new version. Making this change was before me started to work with parallel code parsing, but I believe shared instruction objects have caused too many data races and lock contention between threads. On Tue, Aug 7, 2018 at 2:17 PM William Cohen wrote: > On 05/11/2018 11:21 AM, Xiao

[DynInst_API:] [dyninst/dyninst] 5c0202: 1. The FULL register size must have value 0 due to...

Branch: refs/heads/vector_categories Home: https://github.com/dyninst/dyninst Commit: 5c02025091e1477ec807a2b6d284675b4292631e https://github.com/dyninst/dyninst/commit/5c02025091e1477ec807a2b6d284675b4292631e Author: Xiaozhu Meng Date: 2018-08-21 (Tue, 21 Aug 2018

[DynInst_API:] [dyninst/dyninst] c3a140: After carefully comparing the parsing output of ru...

Branch: refs/heads/new-parallel-parsing Home: https://github.com/dyninst/dyninst Commit: c3a1400592a7aad6136b4f0662d0f8b7971474a7 https://github.com/dyninst/dyninst/commit/c3a1400592a7aad6136b4f0662d0f8b7971474a7 Author: Xiaozhu Meng Date: 2018-08-23 (Thu, 23 Aug 2018

[DynInst_API:] [dyninst/dyninst] b8369b: Fix wrong register operands in x86-64 instruction ...

Branch: refs/heads/master Home: https://github.com/dyninst/dyninst Commit: b8369b5627eec1f7c7ab8ef461dae0b63e20b23d https://github.com/dyninst/dyninst/commit/b8369b5627eec1f7c7ab8ef461dae0b63e20b23d Author: Xiaozhu Meng Date: 2018-08-23 (Thu, 23 Aug 2018) Changed paths

[DynInst_API:] [dyninst/dyninst] 7d9dc0: When the ".debug_info" section is not present, we ...

Branch: refs/heads/master Home: https://github.com/dyninst/dyninst Commit: 7d9dc0d3e6c8d17768c19da8ff09b343585fdab4 https://github.com/dyninst/dyninst/commit/7d9dc0d3e6c8d17768c19da8ff09b343585fdab4 Author: Xiaozhu Meng Date: 2018-08-24 (Fri, 24 Aug 2018) Changed paths

[DynInst_API:] [dyninst/dyninst] 675311: Automatically build boost_atomic

Branch: refs/heads/new-parallel-parsing Home: https://github.com/dyninst/dyninst Commit: 675311c69a546943b131aa00294b41fe286e83e3 https://github.com/dyninst/dyninst/commit/675311c69a546943b131aa00294b41fe286e83e3 Author: Xiaozhu Meng Date: 2018-08-27 (Mon, 27 Aug 2018

[DynInst_API:] [dyninst/dyninst] 7ead1e: The instruction semantics code for push should con...

Branch: refs/heads/master Home: https://github.com/dyninst/dyninst Commit: 7ead1e045f1e7d69e95e7e76a6c6e053ba5ab9cb https://github.com/dyninst/dyninst/commit/7ead1e045f1e7d69e95e7e76a6c6e053ba5ab9cb Author: Xiaozhu Meng Date: 2018-08-27 (Mon, 27 Aug 2018) Changed paths

[DynInst_API:] [dyninst/dyninst] a9cbc9: Added category for vector instructions and initial...

/bf8af5bd315991cdcd946927eb84d27ae76fa1f3 Author: Xiaozhu Meng Date: 2018-06-06 (Wed, 06 Jun 2018) Changed paths: M common/h/dyn_regs.h M common/src/dyn_regs.C Log Message: --- Fix bit-size for YMM and ZMM registers Commit: 12ed82125b72a61357df15bb32a18c1ccbce06f9 https

[DynInst_API:] [dyninst/dyninst] 6c86e9: Fix compilation issue on powerpc

Branch: refs/heads/new-parallel-parsing Home: https://github.com/dyninst/dyninst Commit: 6c86e9a4201eb5921574ccc636512daf9058688c https://github.com/dyninst/dyninst/commit/6c86e9a4201eb5921574ccc636512daf9058688c Author: Xiaozhu Meng Date: 2018-07-06 (Fri, 06 Jul 2018

[DynInst_API:] [dyninst/dyninst] ccebb6: More annotation code to suppress false positives o...

Branch: refs/heads/new-parallel-parsing Home: https://github.com/dyninst/dyninst Commit: ccebb687f1f2a893755ea1bb2970d1eeb9cb32a4 https://github.com/dyninst/dyninst/commit/ccebb687f1f2a893755ea1bb2970d1eeb9cb32a4 Author: Xiaozhu Meng Date: 2018-07-23 (Mon, 23 Jul 2018

Re: [DynInst_API:] commit 45feff81435754b317f980e33a9bad7de4846de5 breaks cmake

b64/ccache/cc -DCHECK_FUNCTION_EXISTS=pthread_create-rdynamic > CMakeFiles/cmTC_6b097.dir/CheckFunctionExists.c.o -o cmTC_6b097 -lpthreads > /usr/bin/ld: cannot find -lpthreads > > > A git bisect showed the failure is triggered by the following patch: > > commit 45feff81435754b31

[DynInst_API:] [dyninst/dyninst] 698f5b: Refactor frame status setter/getter to suppress fa...

Branch: refs/heads/new-parallel-parsing Home: https://github.com/dyninst/dyninst Commit: 698f5b8996071695b250307c376dca62633f888b https://github.com/dyninst/dyninst/commit/698f5b8996071695b250307c376dca62633f888b Author: Xiaozhu Meng Date: 2018-07-24 (Tue, 24 Jul 2018

[DynInst_API:] [dyninst/dyninst] b3796c: Power8 does not necessary have the .opd section

Branch: refs/heads/master Home: https://github.com/dyninst/dyninst Commit: b3796c755f99395da6fc78b5dd6023fda4186fb8 https://github.com/dyninst/dyninst/commit/b3796c755f99395da6fc78b5dd6023fda4186fb8 Author: Xiaozhu Meng Date: 2018-08-28 (Tue, 28 Aug 2018) Changed paths

[DynInst_API:] [dyninst/dyninst] 9d17f8: The fixes for power preamble should not be enabled...

Branch: refs/heads/power8_instrumentation_fix Home: https://github.com/dyninst/dyninst Commit: 9d17f858f26629130def0d817aabd8b34cf992dc https://github.com/dyninst/dyninst/commit/9d17f858f26629130def0d817aabd8b34cf992dc Author: Xiaozhu Meng Date: 2018-09-07 (Fri, 07 Sep 2018

[DynInst_API:] [dyninst/dyninst] b3796c: Power8 does not necessary have the .opd section

Branch: refs/heads/power8_instrumentation_fix Home: https://github.com/dyninst/dyninst Commit: b3796c755f99395da6fc78b5dd6023fda4186fb8 https://github.com/dyninst/dyninst/commit/b3796c755f99395da6fc78b5dd6023fda4186fb8 Author: Xiaozhu Meng Date: 2018-08-28 (Tue, 28 Aug 2018

[DynInst_API:] [dyninst/dyninst] 83855d: Fix non-deterministic parallel parsing on POWER 8....

Branch: refs/heads/new-parallel-parsing Home: https://github.com/dyninst/dyninst Commit: 83855db1d9025169fba1e6b1e9ce114fc8eb5d81 https://github.com/dyninst/dyninst/commit/83855db1d9025169fba1e6b1e9ce114fc8eb5d81 Author: Xiaozhu Meng Date: 2018-09-10 (Mon, 10 Sep 2018

[DynInst_API:] [dyninst/dyninst] 7b75dd: Defer constructing blocksByRange to function final...

Branch: refs/heads/new-parallel-parsing Home: https://github.com/dyninst/dyninst Commit: 7b75dd2f75199ac2ef0706c7f7c5f07fe3401002 https://github.com/dyninst/dyninst/commit/7b75dd2f75199ac2ef0706c7f7c5f07fe3401002 Author: Xiaozhu Meng Date: 2018-07-01 (Sun, 01 Jul 2018

[DynInst_API:] [dyninst/dyninst] 673a94: 1. More static variables should be declared in TLS

Branch: refs/heads/new-parallel-parsing Home: https://github.com/dyninst/dyninst Commit: 673a947c521464bdb38bef8622b0c74563e35ac0 https://github.com/dyninst/dyninst/commit/673a947c521464bdb38bef8622b0c74563e35ac0 Author: Xiaozhu Meng Date: 2018-07-06 (Fri, 06 Jul 2018

[DynInst_API:] [dyninst/dyninst] a9cbc9: Added category for vector instructions and initial...

src/vxworksHeaders.h M symtabAPI/src/emitElf.C Log Message: --- Remove unused rpc/xdr references. Commit: deea7770f63b22de8d22b2fefda5c090ebab8d8c https://github.com/dyninst/dyninst/commit/deea7770f63b22de8d22b2fefda5c090ebab8d8c Author: Xiaozhu Meng Date: 2018-04-17 (Tue, 17

Re: [DynInst_API:] Telling DynInst a particular function is non-returning

Hi Thomas, On Thu, Mar 15, 2018 at 4:06 AM, Thomas Dullien wrote: > Hey there, > > ok, I have looked at a few options on how to best tackle this, and would > love to solicit advice :-) > > - I tried SymtabCodeSource::addNonReturning("__stack_chk_fail"); this did > not

Re: [DynInst_API:] Telling DynInst a particular function is non-returning

es not interpret the tailing call as non-return. > Digging to see what is going on, > will update here as I learn more :) > > Cheers, > Thomas > > > On Thu, Mar 15, 2018 at 1:58 PM, Xiaozhu Meng <mxz...@gmail.com> wrote: > >> Hi Thomas, >> >> On Thu, Mar

Re: [DynInst_API:] codeCoverage build issue with latest master branch git version of Dyninst

Hi Jim, I just recompiled the master branch from github. I saw the same warning, but not the error. Can you try delete your existing cmake cache file and then re-configure the cmake? Thanks, --Xiaozhu On Fri, Apr 13, 2018 at 8:53 AM, Jim Galarowicz wrote: > Hi all, > >

Re: [DynInst_API:] Logging the stack trace

t collect all the return addresses and get all the > stack traces a program makes during its run. So would work if I add this > stack walking code as part of return instrumentation? > > On Monday, 23 April, 2018, 4:50:44 PM GMT-4, Xiaozhu Meng < > mxz...@gmail.com> wrote: >

Re: [DynInst_API:] Logging the stack trace

Hi, Passing (rsp) to your instrumentation function is not going to do what you plan to do because Dyninst's internal instrumentation code will have changed the value of rsp. For us to better help you, can you describe what exactly you would like to do? It seems to me that you are trying to

Re: [DynInst_API:] FATAL 68 Dyninst

Hi Alberto, What's your platform (windows or linux; 32bit or 64bit)? Could you send me the debugging log from DYNINST_DEBUG_STARTUP=1？ Thanks, --Xiaozhu On Tue, Apr 24, 2018 at 4:49 AM, Alberto Olmo wrote: > To whom it may concern, > > My name is Alberto, a student at

[DynInst_API:] [dyninst/dyninst] 16860d: Merge remote-tracking branch 'upstream/master' int...

on/src/ntHeaders.h M common/src/vxworksHeaders.h M symtabAPI/src/emitElf.C Log Message: --- Remove unused rpc/xdr references. Commit: deea7770f63b22de8d22b2fefda5c090ebab8d8c https://github.com/dyninst/dyninst/commit/deea7770f63b22de8d22b2fefda5c090ebab8d8c Au

  1   2   3   4   >