Re: [PATCH v6 04/11] perf tools: Move unwind__prepare_access from thread_new into thread__insert_map

On Sat, May 28, 2016 at 11:59:53AM +, He Kuang wrote: > For determine the libunwind methods to use, we should get the > 32bit/64bit information from maps of a thread. When a thread is newly > created, the information is not prepared. This patch moves > unwind__prepare_access() into

Re: [PATCH v6 04/11] perf tools: Move unwind__prepare_access from thread_new into thread__insert_map

On Sat, May 28, 2016 at 11:59:53AM +, He Kuang wrote: > For determine the libunwind methods to use, we should get the > 32bit/64bit information from maps of a thread. When a thread is newly > created, the information is not prepared. This patch moves > unwind__prepare_access() into

[PATCH v6 04/11] perf tools: Move unwind__prepare_access from thread_new into thread__insert_map

For determine the libunwind methods to use, we should get the 32bit/64bit information from maps of a thread. When a thread is newly created, the information is not prepared. This patch moves unwind__prepare_access() into thread__insert_map() so we can get the information we need from maps.

[PATCH v6 04/11] perf tools: Move unwind__prepare_access from thread_new into thread__insert_map

For determine the libunwind methods to use, we should get the 32bit/64bit information from maps of a thread. When a thread is newly created, the information is not prepared. This patch moves unwind__prepare_access() into thread__insert_map() so we can get the information we need from maps.