On 11/21/2014 01:02 PM, Adrian M Negreanu wrote:
On Fri, Nov 21, 2014 at 7:51 PM, Bill Williams mailto:b...@cs.wisc.edu>> wrote:
On 11/21/2014 11:36 AM, Josh Stone wrote:
On 11/21/2014 01:02 AM, Adrian M Negreanu wrote:
I tried to instrument a strip-ed chrome, as a wo
On Fri, Nov 21, 2014 at 7:51 PM, Bill Williams wrote:
> On 11/21/2014 11:36 AM, Josh Stone wrote:
>
>> On 11/21/2014 01:02 AM, Adrian M Negreanu wrote:
>>
>>> I tried to instrument a strip-ed chrome, as a workaround the
>>> processCreate issue(s) , only to find another problem, this time in
>>> i
On Fri, Nov 21, 2014 at 7:36 PM, Josh Stone wrote:
> On 11/21/2014 01:02 AM, Adrian M Negreanu wrote:
> > I tried to instrument a strip-ed chrome, as a workaround the
> > processCreate issue(s) , only to find another problem, this time in
> > image::findMain()
>
> As a workaround, since you're th
On 11/21/2014 11:36 AM, Josh Stone wrote:
On 11/21/2014 01:02 AM, Adrian M Negreanu wrote:
I tried to instrument a strip-ed chrome, as a workaround the
processCreate issue(s) , only to find another problem, this time in
image::findMain()
As a workaround, since you're the one stripping it, you
On 11/21/2014 01:02 AM, Adrian M Negreanu wrote:
> I tried to instrument a strip-ed chrome, as a workaround the
> processCreate issue(s) , only to find another problem, this time in
> image::findMain()
As a workaround, since you're the one stripping it, you can try
stripping slightly less. Just r
Hi,
I tried to instrument a strip-ed chrome, as a workaround the
processCreate issue(s) , only to find another problem, this time in
image::findMain()
findMain() assumes the entry point address to be an immediate operand:
mov$0x40051b,%rdi
callq 0x77fef3f0
For chrome, I found this in
