Anthony Howe wrote: >> >> Are you possibly catching the signals yourself? > > I trap several signals, but not SIGABRT. > > I handle these myself... > > SIGHUP > SIGINT > SIGQUIT > > And ignore these... > > SIGPIPE > SIGTERM > SIGALRM > SIGXCPU > SIGXFSZ > SIGVTALRM > > The daemon is threaded, so my server API handles; serverSignalsInit sets > up pthread_sigmask to SIG_BLOCK and serverSignalsLoop is the only thread > to receive signals, so other threads do not interfere. Part of my > library code has works fine. > > The issue is core dumps and since SIGABRT should generate a core and I'm > not blocking SIGABRT, the daemon should terminate with a core when I > force SIGABRT. > > It don't. >
Don't know if I understand signals well enough but is it possible you want the default action for SIGABRT instead of ignoring it ?
