Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Oleg V. Zhylin" <ovz@yahoo.com>
To: Jim Blandy <jimb@codesourcery.com>
Cc: gdb@sourceware.org
Subject: Re: gdb Stopped in pthread_create
Date: Tue, 24 Jul 2007 15:50:00 -0000	[thread overview]
Message-ID: <555931.81190.qm@web56602.mail.re3.yahoo.com> (raw)
In-Reply-To: <m3644bgien.fsf@codesourcery.com>

[-- Attachment #1: Type: text/plain, Size: 2333 bytes --]

Hi Jim,

  pthread_test.cpp demonstrates the problematic behavior. It is built
using

 g++ -g pthread_test.cpp -lpthread

 The version numbers are

$ cat /proc/version
Linux version 2.6.21-1.3228.fc7
(kojibuilder@xenbuilder2.fedora.redhat.com) (gcc version 4.1.2 20070502
(Red Hat 4.1.2-12)) #1 SMP Tue Jun 12 15:37:31 EDT 2007

and gdb snapshot for July 24th

$ gdb --version
GNU gdb 6.6.50.20070724

Below is the log of gdb session

$ gdb a.out
GNU gdb 6.6.50.20070724
Copyright (C) 2007 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and
you are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for
details.
This GDB was configured as "i686-pc-linux-gnu"...
Using host libthread_db library "/lib/libthread_db.so.1".
(gdb) run
Starting program: /home/cartcs/Work/gdb/pthread_create/a.out
[Thread debugging using libthread_db enabled]
[New Thread 0xb7f336d0 (LWP 22251)]

[3]+  Stopped                 gdb a.out


--- Jim Blandy <jimb@codesourcery.com> wrote:

> 
> "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.
> 


WBR Oleg V. Zhylin   ovz@yahoo.com


       
____________________________________________________________________________________Ready for the edge of your seat? 
Check out tonight's top picks on Yahoo! TV. 
http://tv.yahoo.com/

[-- Attachment #2: 120145053-pthread_test.cpp --]
[-- Type: application/octet-stream, Size: 721 bytes --]

#include <pthread.h>
#include <sys/time.h>

void Sleep(unsigned long ulMilliseconds)
{
    struct timeval timeout;
    timeout.tv_sec = 0;
    timeout.tv_usec = ulMilliseconds * 1000;
    select(1, NULL, NULL, NULL, &timeout);
} 

static void* threadFunc( void* lpParam ) 
{
   Sleep(3000);
}

int main()
{
  pthread_attr_t attr;

  int		n;
  bool res = false;

  if ( (n = ::pthread_attr_init(&attr)) != 0)
  {
    return -1;
  }
  pthread_t tid;

  if ( (n = ::pthread_create(&tid, &attr, threadFunc, 0)) == 0)
  {

    res = true;
  }

  if ( (n = ::pthread_attr_destroy(&attr)) != 0)
  {
    return -2;
  }
  if (!res)
  {
    return -3;
  }
  Sleep(5000);

  return 0;
}

  parent reply	other threads:[~2007-07-24  9:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-23  9:52 Oleg V. Zhylin
2007-07-23 19:22 ` Jim Blandy
2007-07-24  9:11   ` breaking at thread exit Mayuresh Kulkarni
2007-07-24 15:50   ` Oleg V. Zhylin [this message]
2007-07-28  1:40     ` gdb Stopped in pthread_create Jim Blandy

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=555931.81190.qm@web56602.mail.re3.yahoo.com \
    --to=ovz@yahoo.com \
    --cc=gdb@sourceware.org \
    --cc=jimb@codesourcery.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