| Summary: | ASTERISK-07760: exit() after fork() | ||
| Reporter: | nick gavrikov (nick gavrikov) | Labels: | |
| Date Opened: | 2006-09-18 04:41:16 | Date Closed: | 2006-10-27 12:43:34 |
| Priority: | Minor | Regression? | No |
| Status: | Closed/Complete | Components: | Core/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ( 0) exit.diff | |
| Description: | In many places after fork() in case of some failure child process calls exit(). But this is not right because exit() calls destructors registered with atexit() and some signal handlers. Instead of exit() must be used _exit(). I can write patch for this it you need. | ||
| Comments: | By: Serge Vecher (serge-v) 2006-09-18 10:30:50 Nick: as you are new to the bug-tracker, let me tell you that this is not a good "discussion forum." I think that this issue and ASTERISK-7759 are better of being discussed on the asterisk-dev mailing list first. If the there is enough consensus on the list to prompt a code change, opening a bug report with a patch attached is appropriate at then. Thanks! By: nick gavrikov (nick gavrikov) 2006-09-19 03:45:07 Here is nothing to discuss. This is a bug that can sometimes provide crush. And MOST times - no. You can spend a week trying to reproduce it with no success. I have attached a patch solving a problem. By: Tilghman Lesher (tilghman) 2006-09-19 07:16:42 Please specify how this could crash. By: Russell Bryant (russell) 2006-10-27 12:43:34 fixed in 1.2, 1.4, and trunk in revisions 46361, 46363, and 46364. Thanks! | ||