This is the mail archive of the cygwin@cygwin.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

SIGSEGV when called sem_init() with gdb.


Dear, all

#include <semaphore.h>
int main () {
int p;
sem_t sem;
int i=0,d;
//sem=(sem_t)NULL; //With this There isn't any problem
sem_init (&sem,0,1);
sem_post (&sem);
sem_wait(&sem);
return i;
}

cygwin 1.3.17-1
gcc  3.2-3
gdb  20010428-3

When executing this source code with gdb I get an SIGSEGV signal  when
sem_init() function is called.
If I continue on, program works fine.
If program is not executed from gdb, it works without any error.
If I initialize it with NULL, I don't get any error.

I think that is the same behavior as described by following mail:
http://sources.redhat.com/ml/cygwin/2002-10/msg00956.html
Is this true ?

To avoid annoying gdb error message, is my solution ("sem=(sem_t)NULL")
reliable and portable ?

Best Regards
Oreste Bernardi


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]