From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-42304-listarch-gdb-patches=sources.redhat.com@sourceware.org>
Received: (qmail 20058 invoked by alias); 18 Jan 2006 09:11:17 -0000
Received: (qmail 20038 invoked by uid 22791); 18 Jan 2006 09:11:13 -0000
X-Spam-Check-By: sourceware.org
Received: from svr68.ehostpros.com (HELO svr68.ehostpros.com) (67.15.48.48)     by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 18 Jan 2006 09:11:07 +0000
Received: from [59.95.0.150] (helo=titan.linsyssoft.com) 	by svr68.ehostpros.com with esmtpsa (TLSv1:AES256-SHA:256) 	(Exim 4.52) 	id 1Ez9LK-0002uL-I3; Wed, 18 Jan 2006 01:11:04 -0800
Received: from krypton (krypton [192.168.1.13] (may be forged)) 	by titan.linsyssoft.com (8.13.1/8.13.1) with ESMTP id k0I8vYRd021369; 	Wed, 18 Jan 2006 14:27:34 +0530
Subject: Re: [Patch] Mark the thread_event breakpoint as "not inserted" 	before 	calling thread_mourn_inferior
From: Girish Shilamkar <girish@linsyssoft.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sources.redhat.com
In-Reply-To: <20060117154004.GA3672@nevyn.them.org>
References: <1137512294.3217.29.camel@krypton> 	 <20060117154004.GA3672@nevyn.them.org>
Content-Type: multipart/mixed; boundary="=-VanvPoEw9UbbX+F0uZrI"
Date: Wed, 18 Jan 2006 09:11:00 -0000
Message-Id: <1137575670.3221.17.camel@krypton>
Mime-Version: 1.0
Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-patches-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sourceware.org>
List-Help: <mailto:gdb-patches-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-patches-owner@sourceware.org
X-SW-Source: 2006-01/txt/msg00237.txt.bz2

--=-VanvPoEw9UbbX+F0uZrI
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Content-length: 423

> Definitely not.  We need more information about this bug: what do you
> do to reproduce it, since no one else has encountered it?
> 
I have attached .c to reproduce this bug. I am using gdb-6.4 checked out
from cvs, on Fedora Core 3, 32 bit Athlon processor. To reproduce the
problem just run the application under gdb. No breakpoints, backtrace
etc required. When the application exits this error can be seen.

-Girish.

--=-VanvPoEw9UbbX+F0uZrI
Content-Disposition: attachment; filename=mult.c
Content-Type: text/x-csrc; name=mult.c; charset=utf-8
Content-Transfer-Encoding: 7bit
Content-length: 577

#include <pthread.h>

#define THR_NUMS 5 
#define MAX_THR 512

void *func(void *num)
{
    int i, j, l, m;

    sleep(1);
    for(i=1;i<10;i++)
      {
	for(j=1;j<10;j++)
	  {
	    l = l+j;	    
	  }
      }
}

int main()
{
    int i, thr_nums;
    pthread_t thr[MAX_THR];

    thr_nums = THR_NUMS;    
    for(i=0;i<thr_nums; i++)
      {
	if ( pthread_create (&(thr[i]), NULL, func, &i ) != 0 )
                            perror("Thread creation failed");
      }

    for (i=0;i<thr_nums;i++)    
      {
	    pthread_join( thr[i], NULL);
      }
    return 0;
}
    
    

--=-VanvPoEw9UbbX+F0uZrI--