Re: "fork problem" debugging

2006-05-29 Thread Torfinn Ottesen
Peter Ekberg lysator.liu.se> writes: > > On Sun, May 28, 2006 at 10:40:34PM +, Torfinn Ottesen wrote: > > > > > > I did this for three programs, prog1 (commercial, external), > > prog2 (inhouse, compiled on Cygwin) and native cygwin prog3: > > "echo". I claim tha

Re: "fork problem" debugging

2006-05-29 Thread Peter Ekberg
On Sun, May 28, 2006 at 10:40:34PM +, Torfinn Ottesen wrote: > > I did this for three programs, prog1 (commercial, external), > prog2 (inhouse, compiled on Cygwin) and native cygwin prog3: > "echo". I claim that I saw increased increase memory usage > fo

Re: "fork problem" debugging

2006-05-28 Thread Torfinn Ottesen
Larry Hall (Cygwin cygwin.com> writes: > The key words here are "If you use Registry Editor incorrectly". In other > words, if you modify something other than what's recommended, you might > cause yourself other problems. This is standard boiler-plate legalese that's > spewed whenever mention o

Re: "fork problem" debugging

2006-05-28 Thread Larry Hall (Cygwin)
On 05/28/2006, Torfinn Ottesen wrote: Igor Peshansky cs.nyu.edu> writes: > > On Wed, 17 May 2006, Bryan D. Thomas wrote: >> > > I'm taking the risk of conflating several different >> > > issues into one. On the other hand, this might be a >> > > useful synthesis to help us bottom out on "fork >

Re: "fork problem" debugging

2006-05-28 Thread Torfinn Ottesen
Igor Peshansky cs.nyu.edu> writes: > On Wed, 17 May 2006, Bryan D. Thomas wrote: > > I'm taking the risk of conflating several different > > issues into one. On the other hand, this might be a > > useful synthesis to help us bottom out on "fork > > problems" so that we can turn a snapshot into

Re: "fork problem" debugging

2006-05-18 Thread Igor Peshansky
On Thu, 18 May 2006, Bryan D. Thomas wrote: > "Igor Peshansky" wrote: > > I've been plagued by these problems for a while (since you didn't provide > > full links in your message, I don't know whether you cited my message > > among them without a lot of cutting-and-pasting). > > I didn't cite your

Re: "fork problem" debugging

2006-05-18 Thread Bryan D. Thomas
"Igor Peshansky" wrote: > I've been plagued by these problems for a while (since you didn't provide > full links in your message, I don't know whether you cited my message > among them without a lot of cutting-and-pasting). I didn't cite your message[1], though it was one of the sources of the su

Re: "fork problem" debugging

2006-05-17 Thread Igor Peshansky
On Wed, 17 May 2006, Bryan D. Thomas wrote: > I'm taking the risk of conflating several different > issues into one. On the other hand, this might be a > useful synthesis to help us bottom out on "fork > problems" so that we can turn a snapshot into a stable > release[1]? I've been plagued by th

"fork problem" debugging

2006-05-17 Thread Bryan D. Thomas
I'm taking the risk of conflating several different issues into one. On the other hand, this might be a useful synthesis to help us bottom out on "fork problems" so that we can turn a snapshot into a stable release[1]? I've been trying to figure out strace incantations. Hopefully someone more wiz