I do not know what the shadow stack meant. Is there any idea for the option of
compilation to correct it, and I can handle it quickly not modify your codes .
Owen
-----邮件原件-----
发件人: Josef Weidendorfer [mailto:josef.weidendor...@gmx.de]
发送时间: 2017年6月10日 1:04
收件人: Wuweijia <wuwei...@huawei.com>; valgrind-users@lists.sourceforge.net
抄送: Fanbohao <fanbo...@huawei.com>
主题: Re: 答复: [Valgrind-users] hello there is a question about callgrind on the
arm64.
Sorry, no progress on this front.
If you have any ideas to correctly synchronize real/shadow stack in callgrind
and can do some tests, this would be very welcome!
Josef
Am 05.06.2017 um 10:40 schrieb Wuweijia:
> Josef:
> Hello, is there any news now. when do you can release the patches.
>
> Owen
>
>
> -----邮件原件-----
> 发件人: Josef Weidendorfer [mailto:josef.weidendor...@gmx.de]
> 发送时间: 2017年5月20日 6:24
> 收件人: valgrind-users@lists.sourceforge.net
> 主题: Re: [Valgrind-users] hello there is a question about callgrind on the
> arm64.
>
> Hi Owen,
>
> callgrind currently is somewhat broken on ARM, as the tracking of
> entering/leaving functions is unreliable.
>
> Callgrind heavily uses the stack pointer for that.
> On x86, this works fine, as every call/return changes the SP, but on ARM,
> this is not the case.
>
> There are ideas and at some point, there were patches promised by someone,
> but unfortunately nothing useful up to now...
>
> Josef
>
>
> Am 12.05.2017 um 05:11 schrieb Wuweijia:
>> Hi :
>>
>> I ran the code through the callgrind on the x86-64, it is ok , no
>> recursive cycle existed.
>>
>> But I ran the same the same code through the callgrind on the arm64,
>> it show me there is recursive cycle existed.
>>
>> Between two callgrind.out. file:
>>
>> In arm64:
>>
>> There is function name main’2. It meaning that there is
>> recursive cycle. And it annote the source failed.
>>
>> In x86_64:
>>
>> There is no function name main’2 only main., It mean that
>> there is no cycle.
>>
>> How can I resovle it?
>>
>> The compile options : gcc �Cg �CO0 ./main.cpp
>>
>> The gcc version 4.9
>>
>> Run options: valgrind --tool=callgrind ./a.out
>>
>> Callgrind_annote option callgrind_annote �Cauto=yes
>>
>> BR
>>
>> Owen
>>
>>
>>
>> ---------------------------------------------------------------------
>> -
>> -------- Check out the vibrant tech community on one of the world's
>> most engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>
>>
>>
>> _______________________________________________
>> Valgrind-users mailing list
>> Valgrind-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/valgrind-users
>>
>
>
> ----------------------------------------------------------------------
> -------- Check out the vibrant tech community on one of the world's
> most engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Valgrind-users mailing list
> Valgrind-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/valgrind-users
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users
