From: Girish Shilamkar <girish@linsyssoft.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [Patch] Mark the thread_event breakpoint as "not inserted" before calling thread_mourn_inferior
Date: Wed, 18 Jan 2006 09:11:00 -0000 [thread overview]
Message-ID: <1137575670.3221.17.camel@krypton> (raw)
In-Reply-To: <20060117154004.GA3672@nevyn.them.org>
[-- Attachment #1: Type: text/plain, Size: 423 bytes --]
> 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.
[-- Attachment #2: mult.c --]
[-- Type: text/x-csrc, Size: 577 bytes --]
#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;
}
next prev parent reply other threads:[~2006-01-18 9:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-17 15:35 Girish Shilamkar
2006-01-17 15:40 ` Daniel Jacobowitz
2006-01-18 9:11 ` Girish Shilamkar [this message]
2006-01-18 13:57 ` Daniel Jacobowitz
2006-01-20 14:14 ` Girish Shilamkar
2006-01-20 14:35 ` Daniel Jacobowitz
2006-01-23 9:21 ` Girish Shilamkar
2006-01-24 21:52 ` Daniel Jacobowitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1137575670.3221.17.camel@krypton \
--to=girish@linsyssoft.com \
--cc=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox