15-Nov-16 15:38, Viktor Mihajlovski пишет:
On 15.11.2016 13:19, Peter Krempa wrote:
On Wed, Nov 02, 2016 at 18:56:49 +0300, Maxim Nestratov wrote:
It was introduced by commit 7a51d9ebb, which started to use
monitor commands without job acquiring, which is unsafe and
leads to simultaneous acces
On 15.11.2016 13:19, Peter Krempa wrote:
> On Wed, Nov 02, 2016 at 18:56:49 +0300, Maxim Nestratov wrote:
>> It was introduced by commit 7a51d9ebb, which started to use
>> monitor commands without job acquiring, which is unsafe and
>> leads to simultaneous access to vm->mon structure by different
On 15.11.2016 13:00, Maxim Nestratov wrote:
> 15-Nov-16 14:26, Viktor Mihajlovski пишет:
>
>> On 02.11.2016 17:29, Viktor Mihajlovski wrote:
>>> On 02.11.2016 16:56, Maxim Nestratov wrote:
It was introduced by commit 7a51d9ebb, which started to use
monitor commands without job acquiring,
On Wed, Nov 02, 2016 at 18:56:49 +0300, Maxim Nestratov wrote:
> It was introduced by commit 7a51d9ebb, which started to use
> monitor commands without job acquiring, which is unsafe and leads
> to simultaneous access to vm->mon structure by different threads.
>
> Crash backtrace is the following
15-Nov-16 14:26, Viktor Mihajlovski пишет:
On 02.11.2016 17:29, Viktor Mihajlovski wrote:
On 02.11.2016 16:56, Maxim Nestratov wrote:
It was introduced by commit 7a51d9ebb, which started to use
monitor commands without job acquiring, which is unsafe and leads
to simultaneous access to vm->mon
On 02.11.2016 17:29, Viktor Mihajlovski wrote:
> On 02.11.2016 16:56, Maxim Nestratov wrote:
>> It was introduced by commit 7a51d9ebb, which started to use
>> monitor commands without job acquiring, which is unsafe and leads
>> to simultaneous access to vm->mon structure by different threads.
>>
>>
It was introduced by commit 7a51d9ebb, which started to use
monitor commands without job acquiring, which is unsafe and leads
to simultaneous access to vm->mon structure by different threads.
Crash backtrace is the following (shortened):
Program received signal SIGSEGV, Segmentation fault.
qemuMo
On 02.11.2016 16:56, Maxim Nestratov wrote:
> It was introduced by commit 7a51d9ebb, which started to use
> monitor commands without job acquiring, which is unsafe and leads
> to simultaneous access to vm->mon structure by different threads.
>
> Crash backtrace is the following (shortened):
>
> P
