From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-29170-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 23037 invoked by alias); 23 Jul 2007 17:05:17 -0000
Received: (qmail 23021 invoked by uid 22791); 23 Jul 2007 17:05:16 -0000
X-Spam-Check-By: sourceware.org
Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (65.74.133.4)     by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 23 Jul 2007 17:05:14 +0000
Received: (qmail 8311 invoked from network); 23 Jul 2007 17:05:12 -0000
Received: from unknown (HELO localhost) (jimb@127.0.0.2)   by mail.codesourcery.com with ESMTPA; 23 Jul 2007 17:05:12 -0000
To: "Oleg V. Zhylin" <ovz@yahoo.com>
Cc: gdb@sourceware.org
Subject: Re: gdb Stopped in pthread_create
References: <330935.17438.qm@web56610.mail.re3.yahoo.com>
From: Jim Blandy <jimb@codesourcery.com>
Date: Mon, 23 Jul 2007 19:22:00 -0000
In-Reply-To: <330935.17438.qm@web56610.mail.re3.yahoo.com> (Oleg V. Zhylin's message of "Sat, 21 Jul 2007 07:16:18 -0700 (PDT)")
Message-ID: <m3644bgien.fsf@codesourcery.com>
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-IsSubscribed: yes
Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb.sourceware.org>
List-Subscribe: <mailto:gdb-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-owner@sourceware.org
X-SW-Source: 2007-07/txt/msg00164.txt.bz2


"Oleg V. Zhylin" <ovz@yahoo.com> writes:
>   I've tried to debug my multithreaded application with gdb 6.6 (GNU
> gdb Red Hat Linux (6.6-15.fc7rh) ), but inside pthread_create call I
> get 
>
> [1]+  Stopped                 gdb ./a.out
>
>   If I use ddd on the same machine pthread_create works just fine. 

That's very surprising.  Doesn't DDD just run GDB internally?

> I get this error on all Linux boxes and GUI is not available on all of
> them. Is there a way to configure gdb so that it could tolerate
> pthread_create?

This is a bug; GDB should be able to step over calls to
pthread_create.

If you haven't already, please try downloading the latest GDB sources
from CVS (see http://sourceware.org/gdb/current/) and see if the
problem still occurs.  If it does, then if you can post instructions
here that allow us to reproduce the problem on our own machines, then
I will try to fix it.