Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <003001c2a05c$fd2dae60$940782a4@agr.st.com> From: "Oreste Bernardi" To: Subject: SIGSEGV when called sem_init() with gdb. Date: Tue, 10 Dec 2002 16:01:16 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Dear, all #include 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/