Messages in this thread | | | Subject | Re: glibc-2.0.110/111, apmd3.0beta4, & 2.2.0-final | From | Ulrich Drepper <> | Date | 23 Jan 1999 17:56:31 -0800 |
| |
"Garst R. Reese" <reese@isn.net> writes:
> When I do that I get two messages [104] [105] about apmd exiting. > Seems to be a vfork problem. When I remove the vfork code from > 2.2.0-final by reversing the change in entry.S, all goes well.
This could be what I warned about right from the beginning of the vfork discussion: incorrectly written code. Look through the sources and examine whether vfork is used according to the limitations (no return from the function calling vfork, only _exit or exec called).
-- ---------------. drepper at gnu.org ,-. 1325 Chesapeake Terrace Ulrich Drepper \ ,-------------------' \ Sunnyvale, CA 94089 USA Cygnus Solutions `--' drepper at cygnus.com `------------------------
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |