Comment 6 for bug 540980

Revision history for this message
Michael (michaeljt) wrote :

I actually marked it invalid myself, since I am one of the upstream VirtualBox developers, and as Chase and myself mentioned this is almost certainly VirtualBox-related (if I had initially noticed the "int 3" in the backtrace which Chase pointed out I would not have submitted this in the first place).
I also think that it is fixed upstream now :)
Thanks a lot for your work.