On 01/10/2020 22:32, Walter wrote:
> After a chat with Greg, we agreed on this set of commands
>
>
> trace load /path/to/json process trace start/stop process trace save
> /path/to/json thread trace start/stop thread trace dump [instructions |
> functions]
>
Thanks. The new commands look good t
I'm observing the following deadlock:
One thread calls Module::PreloadSymbols() which takes m_mutex of this Module.
Module::PreloadSymbols()
calls ManualDWARFIndex::Index(), which, in turn, creates thread pool and waits
for all threads completion:
(gdb)
#0 futex_wait_cancelable (private=0, ex
> On Oct 2, 2020, at 3:51 AM, Pavel Labath wrote:
>
> On 01/10/2020 22:32, Walter wrote:
>> After a chat with Greg, we agreed on this set of commands
>>
>>
>> trace load /path/to/json process trace start/stop process trace save
>> /path/to/json thread trace start/stop thread trace dump [instr
Yes this is bad, and GetDescription() is used as a convenience to print out the
module path (which might be a .o file within a .a file) and optionally
architecture of the module. It probably shouldn't be taking the module lock as
the only member variables that that GetDescription accesses are:
