On 5/8/07, Paul Brook <[EMAIL PROTECTED]> wrote:
On Monday 07 May 2007, Samuel Bronson wrote:
> So, if the guest system has a triple-fault, and I had had my mouse grabbed,
> it stays grabbed, so that X has to be restarted (as far as I know).
>
> This happens because abort() doesn't run functions
On Tue, 2007-05-08 at 18:38 +0200, Andreas Schwab wrote:
> Samuel Bronson <[EMAIL PROTECTED]> writes:
> > So, if the guest system has a triple-fault, and I had had my mouse grabbed,
> > it
> > stays grabbed, so that X has to be restarted (as far as I know).
> Not if you have XF86_Ungrab bound to a
Samuel Bronson <[EMAIL PROTECTED]> writes:
> So, if the guest system has a triple-fault, and I had had my mouse grabbed, it
> stays grabbed, so that X has to be restarted (as far as I know).
Not if you have XF86_Ungrab bound to a key.
Andreas.
--
Andreas Schwab, SuSE Labs, [EMAIL PROTECTED]
Su
On Monday 07 May 2007, Samuel Bronson wrote:
> So, if the guest system has a triple-fault, and I had had my mouse grabbed,
> it stays grabbed, so that X has to be restarted (as far as I know).
>
> This happens because abort() doesn't run functions registered with
> atexit(). Suggest use of exit() i
So, if the guest system has a triple-fault, and I had had my mouse grabbed, it
stays grabbed, so that X has to be restarted (as far as I know).
This happens because abort() doesn't run functions registered with atexit().
Suggest use of exit() instead.
