This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
RE: threads/1585: pthread_create generates notify to semaphore when run under gdb
- From: "Barry Reinhold" <bbr at lampreynetworks dot com>
- To: chastain at sourceware dot org
- Cc: gdb-prs at sources dot redhat dot com,
- Date: 28 Aug 2004 15:28:00 -0000
- Subject: RE: threads/1585: pthread_create generates notify to semaphore when run under gdb
- Reply-to: "Barry Reinhold" <bbr at lampreynetworks dot com>
The following reply was made to PR threads/1585; it has been noted by GNATS.
From: "Barry Reinhold" <bbr@lampreynetworks.com>
To: <chastain@sourceware.org>,
<bbr@lampreynetworks.com>,
<chastain@sourceware.org>,
<gdb-prs@sources.redhat.com>,
<gdb-gnats@sources.redhat.com>
Cc:
Subject: RE: threads/1585: pthread_create generates notify to semaphore when run under gdb
Date: Sat, 28 Aug 2004 11:21:05 -0400
I have added code that is essentially:
while(sem_wait(semaphore) != 0 ) {
printf("sem_wait returned non zero..\n");
}
and have seen the non zero returns under the gdb. This is inconsistent
with the man page which documents the return as always being zero.
-----Original Message-----
From: chastain@sourceware.org [mailto:chastain@sourceware.org]
Sent: Saturday, August 28, 2004 10:10 AM
To: bbr@lampreynetworks.com; chastain@sourceware.org;
gdb-prs@sources.redhat.com
Subject: Re: threads/1585: pthread_create generates notify to semaphore
when run under gdb
Synopsis: pthread_create generates notify to semaphore when run under
gdb
State-Changed-From-To: feedback->closed
State-Changed-By: chastain
State-Changed-When: Sat Aug 28 15:09:56 2004
State-Changed-Why:
No feedback received for 30 days.
This is a documented side effect of running threaded programs under
gdb. More signals are generated, and the user application has to cope
with additional signals.
http://sources.redhat.com/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&dat
abase=gdb&pr=1585