Bug 8816 - dump_core_setup() invoked too early in main()
Summary: dump_core_setup() invoked too early in main()
Status: NEW
Alias: None
Product: Samba 3.5
Classification: Unclassified
Component: Winbind (show other bugs)
Version: 3.5.11
Hardware: All All
: P5 normal
Target Milestone: ---
Assignee: Michael Adam
QA Contact: Samba QA Contact
Depends on:
Reported: 2012-03-16 00:07 UTC by Jeff Venable
Modified: 2012-03-16 00:12 UTC (History)
1 user (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Jeff Venable 2012-03-16 00:07:47 UTC
We use a configuration automation framework to spin off winbindd children with auto-generated configuration files and command-line arguments.  If we simulate 'kill -s SIGSEGV' to winbindd, the winbindd!corepath is default compilation value which is invalid.  This causes dump_core() to fail to generate a core file, plus it subsequently invokes exit(1) so it looks like a normal error exit to the parent process.  The parent monitoring process will automatically respin winbindd if it thinks it exited normally with status 0 (EXIT_SUCCESS) or from a signal, but non-zero status exits are considered fatal to avoid infinite fork loops due to bad configurations.

I did a little test moving core_dump_setup() in main() down past the configuration parsing and log setup, and everything works as expected.

Looking at the git history, this appears to be very old and not specific to 3.5.11; I'm merely reporting from the version we're using.