[<<] [<] Page 1 of 1 [>] [>>] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
Signals
From: "Dave Stuart" ####@####.#### Date: 5 Feb 2006 19:14:29 +0000 Message-Id: <001301c62a88$60fcd8e0$2103a8c0@JUSTDAVE> I've put a signal (SIGUSR1) into my application. It seems that nano-x does not like it and is seg faulting. I am compiling nano-x into my application and running under linux. Are there any limitations/rules to nano-x when using signals? thanks dave | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
Re: [nanogui] Signals
From: "Greg Haerr" ####@####.#### Date: 7 Feb 2006 02:34:54 +0000 Message-Id: <01b601c62b8e$e6789390$6401a8c0@winXP> > I've put a signal (SIGUSR1) into my application. It seems that nano-x does not like it and is seg faulting. I am compiling nano-x into my application and running under linux. Are there any limitations/rules to nano-x when using signals? The console-switching functionality uses SIGUNUSED, which is usually SIGUSR1. You'll want to set VTSWITCH=N and things should be OK. Check out the comments in drivers/vtswitch.c. Unless you're linking your application to server, this shouldn't be happening... Regards, Greg | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
Re: [nanogui] Signals
From: "Dave Stuart" ####@####.#### Date: 7 Feb 2006 19:36:10 +0000 Message-Id: <003801c62c1d$b5c7ed10$2103a8c0@JUSTDAVE> I am linking the application into the server. Is this not allowed? dave ----- Original Message ----- From: "Greg Haerr" ####@####.#### To: "Dave Stuart" ####@####.#### ####@####.#### Sent: Monday, February 06, 2006 6:33 PM Subject: Re: [nanogui] Signals >> I've put a signal (SIGUSR1) into my application. It seems that nano-x > does not like it and is seg faulting. I am compiling nano-x into my > application and running under linux. > Are there any limitations/rules to nano-x when using signals? > > The console-switching functionality uses SIGUNUSED, which is usually > SIGUSR1. You'll want to set VTSWITCH=N and things should be > OK. Check out the comments in drivers/vtswitch.c. Unless you're > linking your application to server, this shouldn't be happening... > > Regards, > > Greg > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: ####@####.#### > For additional commands, e-mail: ####@####.#### > | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
Re: [nanogui] Signals
From: "Greg Haerr" ####@####.#### Date: 8 Feb 2006 01:54:09 +0000 Message-Id: <05b001c62c52$78f74810$6401a8c0@winXP> : I am linking the application into the server. Is this not allowed? The point was that if you didn't link app to server, then the server wouldn't be getting your client's signals, since they'd be seperate processes. Regards, Greg : : >> I've put a signal (SIGUSR1) into my application. It seems that nano-x : > does not like it and is seg faulting. I am compiling nano-x into my : > application and running under linux. : > Are there any limitations/rules to nano-x when using signals? : > : > The console-switching functionality uses SIGUNUSED, which is usually : > SIGUSR1. You'll want to set VTSWITCH=N and things should be : > OK. Check out the comments in drivers/vtswitch.c. Unless you're : > linking your application to server, this shouldn't be happening... : > : > Regards, : > : > Greg : > : > : > --------------------------------------------------------------------- : > To unsubscribe, e-mail: ####@####.#### : > For additional commands, e-mail: ####@####.#### : > : : --------------------------------------------------------------------- : To unsubscribe, e-mail: ####@####.#### : For additional commands, e-mail: ####@####.#### : : | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
[<<] [<] Page 1 of 1 [>] [>>] |