Robert Collins wrote:
Because the results are undefined, you are permitted to return EBUSY...
Linux and Solaris do not return an error when the attr is already
initialized, therefore i will do the change to return 0.
The code must be changed anyway, since some attr_init functions
erroneously ret
Because the results are undefined, you are permitted to return EBUSY...
Rob
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
Rasmus Hahn wrote:
Hi Thomas,
Problem solved: it was not the mutex but the but the pthread_mutexattr_t
that caused the error. cygwin's pthread_mutexattr_init () function checks
if its argument points to a valid object. If the pthread_mutexattr_t's
value still points to a valid object (from a prev
Hi Thomas,
Problem solved: it was not the mutex but the but the pthread_mutexattr_t
that caused the error. cygwin's pthread_mutexattr_init () function checks
if its argument points to a valid object. If the pthread_mutexattr_t's
value still points to a valid object (from a previous call)
pthread
Rasmus Hahn wrote:
On Tue, Jun 10, 2003 at 09:25:43AM +0200, Thomas Pfaff wrote:
Rasmus Hahn wrote:
Hello,
i am using cygwin on my Windows2000 and my c++ program segfaults
when using pthread-mutexes. In particular i am using a lot of
mutexes from within constructors of static objects. These con
Hello Larry,
this bug does not show up in gcc-3.3 (i use it already and it works from
my point of view) so we really can look forward (and look forward to the
new, yet unknown bugs they have built in, too).
Greetings - Rasmus
On Mon, Jun 09, 2003 at 10:14:18PM -0400, Larry Hall wrote:
> Hi Rasmu
On Tue, Jun 10, 2003 at 09:25:43AM +0200, Thomas Pfaff wrote:
> Rasmus Hahn wrote:
>
> > Hello,
> >
> > i am using cygwin on my Windows2000 and my c++ program segfaults
> > when using pthread-mutexes. In particular i am using a lot of
> > mutexes from within constructors of static objects. These
Rasmus Hahn wrote:
Hello,
i am using cygwin on my Windows2000 and my c++ program segfaults
when using pthread-mutexes. In particular i am using a lot of
mutexes from within constructors of static objects. These constructors
are called at a very early time of execution of the program and do
calls
However, the cygwin-gcc is not a 3.3 and is has some bugs. Since the cygwin
dll source is in large parts c++ i thought some bugs of the `wrong-code'-kind
could creep into cygwin1.dll. Since i do not know the innards of cygwin
very well i recompiled the dll just to be sure, but i dont really know if
Rasmus Hahn wrote:
BTW i am using cygwin snapshot 20030602 compiled with gcc-3.3 since the
out-of-the-box gcc from the cygwin-package is a prerelease and definitely
contains bugs that do not allow it to compile my code.
As previously mentioned on this list, the gcc that comes with Cygwin is
vers
10 matches
Mail list logo