On Fri, Apr 21, 2017 at 09:47:51AM +0200, Wouter Verhelst wrote:
> On Fri, Apr 21, 2017 at 09:17:35AM +0200, Wouter Verhelst wrote:
> > I haven't been able to reproduce this either, so it might be something
> > complicated.
>
> Actually, scratch that, I have. It appears to happen if I single-step
> through the function that sends the INFO message, rather than allowing
> it to run "normally".
It turns out in the end that this was actually on the master branch, not
the nbd one; and it happens when single-stepping a client that's
connected to a qemu nbd server, regardless of where in the conversation.
It feels like a race condition somewhere, but I haven't been able to
track it down yet.
--
< ron> I mean, the main *practical* problem with C++, is there's like a dozen
people in the world who think they really understand all of its rules,
and pretty much all of them are just lying to themselves too.
-- #debian-devel, OFTC, 2016-02-12
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Nbd-general mailing list
Nbd-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nbd-general
