Messages in this thread | | | Date | Sat, 23 Jan 1999 23:00:01 -0400 | From | "Garst R. Reese" <> | Subject | Re: glibc-2.0.110/111, apmd3.0beta4, & 2.2.0-final |
| |
Ulrich Drepper wrote: > > "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). > I replaced apmd with r.gooch's suspendd, and all is well with glibc-2.0.111, egcs-1.1.1, and linux-2.2.0-final. Get it from: http://atnf.csiro.au/~rgooch/linux Thanks to all --esp. Richard. -- Garst
- 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/
| |