| Date: | Mon, 24 Jul 2017 12:16:59 +0200 |
|---|---|
| From: | Thomas Dullien <thomasdullien@xxxxxxxxxx> |
| Subject: | [DynInst_API:] Concurrent calls to getInsns |
|
Hey there,
I am observing data races and inconsistent results when multiple threads run through the following code: Dyninst::ParseAPI::Block::Insns block_instructions; block->getInsns(block_instructions); for (const auto& instruction : block_instructions) { .... } Are Dyninst functions thread-unsafe by default, or what is the best way of finding out which ones are safe and which ones aren't ? :-) Cheers, Thomas PS: Thanks for the awesome tool ! :) |
| [← Prev in Thread] | Current Thread | [Next in Thread→] |
|---|---|---|
| ||
| Previous by Date: | [DynInst_API:] [dyninst/dyninst], jdetter |
|---|---|
| Next by Date: | Re: [DynInst_API:] Concurrent calls to getInsns, Bill Williams |
| Previous by Thread: | Re: [DynInst_API:] Compiling CFGTool using Dyninst Libarary in Ubuntu 16.04, Sazzadur Rahaman |
| Next by Thread: | Re: [DynInst_API:] Concurrent calls to getInsns, Bill Williams |
| Indexes: | [Date] [Thread] |