On Tue, Jan 10, 2017 at 07:22:24PM -0600, Doug Goldstein wrote:
> On 1/10/17 10:01 AM, Stefan Hajnoczi wrote:
> > On Mon, Jan 09, 2017 at 01:08:53PM +, Dr. David Alan Gilbert wrote:
> >> copying in Stefan since it's his commit.
> >
> > I can't reproduce the assertion failure.
> >
> > Are you
On 1/10/17 10:01 AM, Stefan Hajnoczi wrote:
> On Mon, Jan 09, 2017 at 01:08:53PM +, Dr. David Alan Gilbert wrote:
>> copying in Stefan since it's his commit.
>
> I can't reproduce the assertion failure.
>
> Are you able to provide a backtrace (e.g. launch QEMU under gdb and then
> use the
On Mon, Jan 09, 2017 at 01:08:53PM +, Dr. David Alan Gilbert wrote:
> copying in Stefan since it's his commit.
>
> * Doug Goldstein (car...@cardoe.com) wrote:
> > I'm currently hitting an assert on master. I've bisected the change down
> > to aff8fd18f1786fc5af259a9bc0077727222f51ca but
copying in Stefan since it's his commit.
* Doug Goldstein (car...@cardoe.com) wrote:
> I'm currently hitting an assert on master. I've bisected the change down
> to aff8fd18f1786fc5af259a9bc0077727222f51ca but obviously that's a false
> positive because that adds the assert for the condition. So
I'm currently hitting an assert on master. I've bisected the change down
to aff8fd18f1786fc5af259a9bc0077727222f51ca but obviously that's a false
positive because that adds the assert for the condition. So obviously
the issue was introduced prior to this. As another data point the issue
only