[DynInst_API:] [PATCH dyninstAPI v2] Reallocate memory map buffer exponentially until there is enough space for the whole map.

From: Francis Deslauriers Starting from the default size buffer, we try to read the memory map without allocating new space. If we reach the end of the buffer before the end of the file, we allocate a buffer twice as big and try again. When we reach the MAX_MAP_SIZE we return an error to the call

[DynInst_API:] [PATCH dyninstAPI] Reallocate memory map buffer exponentially until there is enough space for the whole map.

From: Francis Deslauriers Starting from the default size buffer, we try to read the memory map without allocating new space. If we reach the end of the buffer before the end of the file, we allocate a buffer twice as big and try again. When we reach the MAX_MAP_SIZE we return an error to the call

Re: [DynInst_API:] Correlating VariableLocation with Expression::Ptr

On 07/12/2014 02:16 PM, Ashay Rane wrote: Hello, I am trying to limit the instructions that need to be instrumented based on information from SymtabAPI. Using SymtabAPI, I have the VariableLocation information like: stClass: storageRegOffset, refClass: storageNoRef, mr_reg: x86_64::rsp, frame_o

[DynInst_API:] Correlating VariableLocation with Expression::Ptr

Hello, I am trying to limit the instructions that need to be instrumented based on information from SymtabAPI. Using SymtabAPI, I have the VariableLocation information like: stClass: storageRegOffset, refClass: storageNoRef, mr_reg: x86_64::rsp, frame_offset: fff159d8, low-pc: 0x4004f4, h

Re: [DynInst_API:] Runtime Relocation Mechanism

On 07/11/2014 08:24 PM, Buddhika Chamith Kahawitage Don wrote: Hi All, Feel free redirect me to the correct place if this query is not relevant to this particular list. I understand that DynInst uses a runtime code relocation mechanism for inserting instrumentation. I am interested in knowing sp