在 2016/5/10 19:59, Adrian Hunter 写道:
On 10/05/16 14:38, Hekuang wrote:
在 2016/5/10 18:34, Adrian Hunter 写道:
On 10/05/16 12:49, Hekuang wrote:
hi
在 2016/5/10 16:08, Adrian Hunter 写道:
On 10/05/16 10:40, He Kuang wrote:
32-bit programs can be run on 64-bit machines, so we should choose
在 2016/5/10 19:59, Adrian Hunter 写道:
On 10/05/16 14:38, Hekuang wrote:
在 2016/5/10 18:34, Adrian Hunter 写道:
On 10/05/16 12:49, Hekuang wrote:
hi
在 2016/5/10 16:08, Adrian Hunter 写道:
On 10/05/16 10:40, He Kuang wrote:
32-bit programs can be run on 64-bit machines, so we should choose
On 10/05/16 14:38, Hekuang wrote:
>
>
> 在 2016/5/10 18:34, Adrian Hunter 写道:
>> On 10/05/16 12:49, Hekuang wrote:
>>> hi
>>>
>>> 在 2016/5/10 16:08, Adrian Hunter 写道:
On 10/05/16 10:40, He Kuang wrote:
> 32-bit programs can be run on 64-bit machines, so we should choose
> unwind
On 10/05/16 14:38, Hekuang wrote:
>
>
> 在 2016/5/10 18:34, Adrian Hunter 写道:
>> On 10/05/16 12:49, Hekuang wrote:
>>> hi
>>>
>>> 在 2016/5/10 16:08, Adrian Hunter 写道:
On 10/05/16 10:40, He Kuang wrote:
> 32-bit programs can be run on 64-bit machines, so we should choose
> unwind
在 2016/5/10 18:34, Adrian Hunter 写道:
On 10/05/16 12:49, Hekuang wrote:
hi
在 2016/5/10 16:08, Adrian Hunter 写道:
On 10/05/16 10:40, He Kuang wrote:
32-bit programs can be run on 64-bit machines, so we should choose
unwind methods according to 'thread->map' instead of the host
architecture.
在 2016/5/10 18:34, Adrian Hunter 写道:
On 10/05/16 12:49, Hekuang wrote:
hi
在 2016/5/10 16:08, Adrian Hunter 写道:
On 10/05/16 10:40, He Kuang wrote:
32-bit programs can be run on 64-bit machines, so we should choose
unwind methods according to 'thread->map' instead of the host
architecture.
On 10/05/16 12:49, Hekuang wrote:
> hi
>
> 在 2016/5/10 16:08, Adrian Hunter 写道:
>> On 10/05/16 10:40, He Kuang wrote:
>>> 32-bit programs can be run on 64-bit machines, so we should choose
>>> unwind methods according to 'thread->map' instead of the host
>>> architecture.
>>>
>>> This patch adds
On 10/05/16 12:49, Hekuang wrote:
> hi
>
> 在 2016/5/10 16:08, Adrian Hunter 写道:
>> On 10/05/16 10:40, He Kuang wrote:
>>> 32-bit programs can be run on 64-bit machines, so we should choose
>>> unwind methods according to 'thread->map' instead of the host
>>> architecture.
>>>
>>> This patch adds
hi
在 2016/5/10 16:08, Adrian Hunter 写道:
On 10/05/16 10:40, He Kuang wrote:
32-bit programs can be run on 64-bit machines, so we should choose
unwind methods according to 'thread->map' instead of the host
architecture.
This patch adds methods to test whether a dso is 64-bit or 32-bit by
the
hi
在 2016/5/10 16:08, Adrian Hunter 写道:
On 10/05/16 10:40, He Kuang wrote:
32-bit programs can be run on 64-bit machines, so we should choose
unwind methods according to 'thread->map' instead of the host
architecture.
This patch adds methods to test whether a dso is 64-bit or 32-bit by
the
On 10/05/16 10:40, He Kuang wrote:
> 32-bit programs can be run on 64-bit machines, so we should choose
> unwind methods according to 'thread->map' instead of the host
> architecture.
>
> This patch adds methods to test whether a dso is 64-bit or 32-bit by
> the class info in elf.
What about
On 10/05/16 10:40, He Kuang wrote:
> 32-bit programs can be run on 64-bit machines, so we should choose
> unwind methods according to 'thread->map' instead of the host
> architecture.
>
> This patch adds methods to test whether a dso is 64-bit or 32-bit by
> the class info in elf.
What about
32-bit programs can be run on 64-bit machines, so we should choose
unwind methods according to 'thread->map' instead of the host
architecture.
This patch adds methods to test whether a dso is 64-bit or 32-bit by
the class info in elf.
Signed-off-by: He Kuang
---
32-bit programs can be run on 64-bit machines, so we should choose
unwind methods according to 'thread->map' instead of the host
architecture.
This patch adds methods to test whether a dso is 64-bit or 32-bit by
the class info in elf.
Signed-off-by: He Kuang
---
tools/perf/util/symbol-elf.c |
14 matches
Mail list logo