public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: "Sébastien Roret" <sroret@eprocess.fr>
Cc: gdb@sources.redhat.com
Subject: Re: fork and pthreads
Date: Fri, 30 Sep 2005 13:08:00 -0000	[thread overview]
Message-ID: <20050930130802.GA7043@nevyn.them.org> (raw)
In-Reply-To: <loom.20050930T114252-296@post.gmane.org>

On Fri, Sep 30, 2005 at 09:58:05AM +0000, Sébastien Roret wrote:
> Hi, 
>  
> I'm having some problems using fork() with threads. 
> I'm using a debian linux on Intel, gdb 6.3, glibc 2.3.3 and 2.3.5 
> If I call forks before using threads it's ok, but not the other way. 
> The problem occurs only with gdb. 
> See below the testcase and output I got. 
> My question : is it a bug, or did I missed something ? 

Please try a CVS snapshot (6.3.50.*) and let us know if that works
better.


-- 
Daniel Jacobowitz
CodeSourcery, LLC

  reply	other threads:[~2005-09-30 13:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-30 10:23 Sébastien Roret
2005-09-30 13:08 ` Daniel Jacobowitz [this message]
2005-09-30 14:49 ` Sébastien Roret

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=20050930130802.GA7043@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb@sources.redhat.com \
    --cc=sroret@eprocess.fr \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).