Re: puzzled: fork +libthr

2011-04-17 Thread Andriy Gapon
on 18/04/2011 03:54 Alexander Kabaev said the following: > > I would blame it, and expressly at that. -pthread is a shortcut for > {-lpthread -lc} instead of just {-lc} in the place where implied libc > is provided by the compiler driver and has no magic properties you want > it it to have. If chr

Re: puzzled: fork +libthr

2011-04-17 Thread Alexander Kabaev
On Sun, 17 Apr 2011 18:56:52 +0300 Andriy Gapon wrote: > on 17/04/2011 18:21 Daniel Eischen said the following: > > On Sun, 17 Apr 2011, Andriy Gapon wrote: > > > >> on 16/04/2011 14:46 Andriy Gapon said the following: > >>> The second puzzle is the EPERM return value itself, on stable/8. > >>>

Re: puzzled: fork +libthr

2011-04-17 Thread Alexander Kabaev
On Sun, 17 Apr 2011 17:39:43 +0300 Andriy Gapon wrote: > on 16/04/2011 14:46 Andriy Gapon said the following: > > The second puzzle is the EPERM return value itself, on stable/8. > > From what I seem chromium does a bunch of forks before it gets to > > the place of interest. My debugging shows t

Re: puzzled: fork +libthr

2011-04-17 Thread Daniel Eischen
On Sun, 17 Apr 2011, Andriy Gapon wrote: on 17/04/2011 18:21 Daniel Eischen said the following: On Sun, 17 Apr 2011, Andriy Gapon wrote: on 16/04/2011 14:46 Andriy Gapon said the following: The second puzzle is the EPERM return value itself, on stable/8. From what I seem chromium does a bunc

Re: puzzled: fork +libthr

2011-04-17 Thread Andriy Gapon
on 17/04/2011 18:21 Daniel Eischen said the following: > On Sun, 17 Apr 2011, Andriy Gapon wrote: > >> on 16/04/2011 14:46 Andriy Gapon said the following: >>> The second puzzle is the EPERM return value itself, on stable/8. >>> From what I seem chromium does a bunch of forks before it gets to the

Re: puzzled: fork +libthr

2011-04-17 Thread Daniel Eischen
On Sun, 17 Apr 2011, Andriy Gapon wrote: on 16/04/2011 14:46 Andriy Gapon said the following: The second puzzle is the EPERM return value itself, on stable/8. From what I seem chromium does a bunch of forks before it gets to the place of interest. My debugging shows that those forks are "singl

Re: puzzled: fork +libthr

2011-04-17 Thread Andriy Gapon
on 16/04/2011 14:46 Andriy Gapon said the following: > The second puzzle is the EPERM return value itself, on stable/8. > From what I seem chromium does a bunch of forks before it gets to the place of > interest. My debugging shows that those forks are "single-threaded" (i.e. > code > in thr_fork

Re: puzzled: fork +libthr

2011-04-17 Thread Andriy Gapon
on 16/04/2011 14:46 Andriy Gapon said the following: > > Guys, > > I am trying to debug this chromium issue: > http://trillian.chruetertee.ch/chromium/ticket/13 > Not sure SOCK_SEQPACKET mentioned in the ticket is an actual culprit, the > problem that interests me is that pthread_cond_wait() retu

puzzled: fork +libthr

2011-04-16 Thread Andriy Gapon
Guys, I am trying to debug this chromium issue: http://trillian.chruetertee.ch/chromium/ticket/13 Not sure SOCK_SEQPACKET mentioned in the ticket is an actual culprit, the problem that interests me is that pthread_cond_wait() returns EPERM where it shouldn't. That happens on stable/8. I compare