I presume that you know signals and signal handlers in general.
Csound "catches" some signals (see sigs[]) only to say

  Csound tidy up etc..

where "etc" is defined from csound.c:762

  Hangup
  Interrupt
  ...

With `CSOUNDINIT_NO_SIGNAL_HANDLER' you can handle (block, ignore, or other)
these signals in your app.

tito

On Tue, May 29, 2012 at 11:23:47PM -0700, Alex Weiss wrote:
> Thanks Tito, I just found it in the sources. Pardon my ignorance, but what
> exactly does the signal handler do, and why would/wouldn't I want it?
> 
> Alex
> 
> On Tue, May 29, 2012 at 11:20 PM, Tito Latini <tito.01beta@gmail.com> wrote:
> 
> > > What exactly does the "flags" parameter in csoundInitialize do? I
> > couldn't
> > > find anything in the docs about it, but for some reason my host always
> > > crashes when it is set to 0, and works when nonzero...
> >
> > The cause of the crash is the signal handler, in particular
> > SIGSEGV in the sigs[] array Top/csound.c:910
> >
> > The flags for `csoundInitialize' are in csound.h:286
> >
> >  #define CSOUNDINIT_NO_SIGNAL_HANDLER  1
> >  #define CSOUNDINIT_NO_ATEXIT          2
> >
> > so `csoundInitialize(argc, argv, CSOUNDINIT_NO_SIGNAL_HANDLER)`
> > resolves your problem.
> >
> > tito

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net