Re: Signal handling in WIN32 console programs

2009-01-23 Thread avadekar
On Fri, Jan 23, 2009 at 05:10:34AM -0500, Corinna Vinschen wrote: > On Jan 22 18:05, avade...@certicom.com wrote: > > On Thu, Jan 22, 2009 at 05:04:23PM -0500, Christopher Faylor wrote: > > > On Thu, Jan 22, 2009 at 09:58:08PM +, Andy Koppe wrote: > > > > avade...@certicom.com wrote: > > > >>

Re: Signal handling in WIN32 console programs

2009-01-23 Thread Corinna Vinschen
On Jan 22 18:05, avade...@certicom.com wrote: > On Thu, Jan 22, 2009 at 05:04:23PM -0500, Christopher Faylor wrote: > > On Thu, Jan 22, 2009 at 09:58:08PM +, Andy Koppe wrote: > > > avade...@certicom.com wrote: > > >> So I > > >>wonder if the native console passes the character to the process

Re: Signal handling in WIN32 console programs

2009-01-22 Thread avadekar
On Thu, Jan 22, 2009 at 05:04:23PM -0500, Christopher Faylor wrote: > On Thu, Jan 22, 2009 at 09:58:08PM +, Andy Koppe wrote: > > avade...@certicom.com wrote: > >>My WIN32 app is compiled under vc7 and uses signal() to trap SIGINT, > >>SIGABRT and SIGTERM. If I run the application under consol

Re: Signal handling in WIN32 console programs

2009-01-22 Thread Christopher Faylor
On Thu, Jan 22, 2009 at 09:58:08PM +, Andy Koppe wrote: > avade...@certicom.com wrote: >>My WIN32 app is compiled under vc7 and uses signal() to trap SIGINT, >>SIGABRT and SIGTERM. If I run the application under console2 or a >>native terminal, pressing ^C triggers the handler and the applicat

Re: Signal handling in WIN32 console programs

2009-01-22 Thread Andy Koppe
avade...@certicom.com wrote: My WIN32 app is compiled under vc7 and uses signal() to trap SIGINT, SIGABRT and SIGTERM. If I run the application under console2 or a native terminal, pressing ^C triggers the handler and the application stops programmatically due to a state change made by the handl

Signal handling in WIN32 console programs

2009-01-19 Thread avadekar
I ran across something under minTTY that I've confirmed behaves the same way in rxvt, but differs under both the native terminal and console2. I expect there is a good reason why this happens, and I'm quite willing to modify the WIN32 app rather than pine for a change in minTTY to accomodate me.