Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Joel Brobecker <brobecker@gnat.com>, msnyder@redhat.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA/testsuite] backtrace past pthread_cond_wait()
Date: Fri, 05 Mar 2004 03:39:00 -0000	[thread overview]
Message-ID: <20040305033910.GE5320@nevyn.them.org> (raw)
In-Reply-To: <20031120073458.GE504@gnat.com>

On Wed, Nov 19, 2003 at 11:34:58PM -0800, Joel Brobecker wrote:
> Hello,
> 
> Re: http://sources.redhat.com/ml/gdb-patches/2003-10/msg00440.html
> 
> Here is a new test that would verify that GDB is able to unwind past
> pthread_cond_wait(). On my laptop, I get all PASS, while on a RH9.0
> machine I get one FAIL.

On Debian unstable I get all PASS, with both LinuxThreads and NPTL. 
Not bad.  Didn't even have to use the system's separate debug info
(I keep the debug info in /usr/lib/debug and my test GDB tree pointed
at /usr/local/lib/debug, usually).

> I am not too familiar with pthreads, so I hope my program is
> portable. In particular, I am worried about cygwin... Some guidance
> would be much appreciated (in Ada, we use tasks, which syntax and
> behavior is defined by the Ada Reference Manual, so the issue about
> portability is left to the compiler/runtime developers).
> 
> 2003-11-19  J. Brobecker  <brobecker@gnat.com>
> 
>         * gdb.threads/pt.c: New file.
>         * gdb.threads/pthread_cond_wait.exp: New test.
> 
> OK to apply?

My only complaint is about pt.c - please use a more descriptive name.
The test itself looks OK.  I would be happier if you didn't play games
with info threads; the order in which GDB will discover threads is
actually somewhat random using gdbserver, since new threads are not
notified.  But this should be OK anyway.

Michael Snyder is the listed maintainer of gdb.threads.  Michael?

> 
> Thanks,
> -- 
> Joel

> /* A small multi-threaded test case.
> 
>    Copyright 2003
>    Free Software Foundation, Inc.
> 
>    This file is part of GDB.
> 
>    This program is free software; you can redistribute it and/or modify
>    it under the terms of the GNU General Public License as published by
>    the Free Software Foundation; either version 2 of the License, or
>    (at your option) any later version.
> 
>    This program is distributed in the hope that it will be useful,
>    but WITHOUT ANY WARRANTY; without even the implied warranty of
>    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
>    GNU General Public License for more details.
> 
>    You should have received a copy of the GNU General Public License
>    along with this program; if not, write to the Free Software
>    Foundation, Inc., 59 Temple Place - Suite 330,
>    Boston, MA 02111-1307, USA.  */
> 
> #include <pthread.h>
> #include <stdio.h>
> #include <time.h>
> 
> void
> cond_wait (pthread_cond_t *cond, pthread_mutex_t *mut)
> {
>   pthread_mutex_lock(mut);
>   pthread_cond_wait (cond, mut);
>   pthread_mutex_unlock (mut);
> }
> 
> void
> noreturn (void)
> {
>   pthread_mutex_t mut;
>   pthread_cond_t cond;
> 
>   pthread_mutex_init (&mut, NULL);
>   pthread_cond_init (&cond, NULL);
> 
>   /* Wait for a condition that will never be signaled, so we effectively
>      block the thread here.  */
>   cond_wait (&cond, &mut);
> }
> 
> void *
> forever_pthread (void *unused)
> {
>   noreturn ();
> }
> 
> void
> break_me (void)
> {
>   /* Just an anchor to help putting a breakpoint.  */
> }
> 
> int
> main (void)
> {
>   pthread_t forever;
>   const struct timespec ts = { 0, 10000000 }; /* 0.01 sec */
> 
>   pthread_create (&forever, NULL, forever_pthread, NULL);
>   for (;;)
>     {
>       nanosleep (&ts, NULL);
>       break_me();
>     }
> 
>   return 0;
> }
> 

> # Copyright (C) 2003 Free Software Foundation, Inc.
> 
> # This program is free software; you can redistribute it and/or modify
> # it under the terms of the GNU General Public License as published by
> # the Free Software Foundation; either version 2 of the License, or
> # (at your option) any later version.
> # 
> # This program is distributed in the hope that it will be useful,
> # but WITHOUT ANY WARRANTY; without even the implied warranty of
> # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
> # GNU General Public License for more details.
> # 
> # You should have received a copy of the GNU General Public License
> # along with this program; if not, write to the Free Software
> # Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.  
> 
> # Please email any bugs, comments, and/or additions to this file to:
> # bug-gdb@gnu.org
> 
> # This file was written by Joel Brobecker.
> #
> # It verifies that GDB is able to compute a backtrace for a thread
> # being blocked on a call to pthread_cond_wait(). 
> 
> if $tracelevel then {
> 	strace $tracelevel
> }
> 
> set testfile "pt"
> set srcfile ${testfile}.c
> set binfile ${objdir}/${subdir}/${testfile}
> 
> if {[gdb_compile_pthreads "${srcdir}/${subdir}/${srcfile}" "${binfile}" executable [list debug "incdir=${objdir}"]] != "" } {
>     return -1
> }
> 
> gdb_exit
> gdb_start
> gdb_reinitialize_dir $srcdir/$subdir
> gdb_load ${binfile}
> 
> gdb_test "break break_me" \
>          "Breakpoint 1 at .*: file .*pt.c, line .*" \
>          "breakpoint on break_me"
> 
> gdb_test "run" \
>          ".*Breakpoint 1, break_me ().*" \
>          "run to break_me"
> 
> # Depending on the thread implementation (Linux Threads, NPTL, etc...),
> # The number of threads known to GDB may vary. We should have at least
> # two threads, but we may have more. We want to switch to the pthread
> # we created via pthread_create, and its ID should be the highest ID
> # of all threads known to GDB.
> set thread_id ""
> send_gdb "info threads\n"
> gdb_expect {
>     -re "\s*(\[0-9\]+) Thread.*$gdb_prompt $" {
>         set thread_id $expect_out(1,string)
>     }
>     default {
>         fail "Unable to find thread id, defaulting to 2"
>         set thread_id "2"
>     }
> }
>     
> 
> # Switch to thread 2, which is doing a forever wait...
> gdb_test "thread $thread_id" \
>          ".*Switching to thread $thread_id.*" \
>          "switching to thread $thread_id"
> 
> # Verify that we are able to get a sensible backtrace, including
> # the frame for the pthread_cond_wait() call.
> gdb_test "backtrace" \
>          ".*pthread_cond_wait.*cond_wait.*noreturn.*forever_pthread.*" \
>          "backtrace in blocked thread"
> 


-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


WARNING: multiple messages have this Message-ID
From: Daniel Jacobowitz <drow@false.org>
To: Joel Brobecker <brobecker@gnat.com>, msnyder@redhat.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA/testsuite] backtrace past pthread_cond_wait()
Date: Fri, 19 Mar 2004 00:09:00 -0000	[thread overview]
Message-ID: <20040305033910.GE5320@nevyn.them.org> (raw)
Message-ID: <20040319000900.nhBvy8Lxlaiw655jTqHLrdIyAz6-ZfKTHzkJRSn05VM@z> (raw)
In-Reply-To: <20031120073458.GE504@gnat.com>

On Wed, Nov 19, 2003 at 11:34:58PM -0800, Joel Brobecker wrote:
> Hello,
> 
> Re: http://sources.redhat.com/ml/gdb-patches/2003-10/msg00440.html
> 
> Here is a new test that would verify that GDB is able to unwind past
> pthread_cond_wait(). On my laptop, I get all PASS, while on a RH9.0
> machine I get one FAIL.

On Debian unstable I get all PASS, with both LinuxThreads and NPTL. 
Not bad.  Didn't even have to use the system's separate debug info
(I keep the debug info in /usr/lib/debug and my test GDB tree pointed
at /usr/local/lib/debug, usually).

> I am not too familiar with pthreads, so I hope my program is
> portable. In particular, I am worried about cygwin... Some guidance
> would be much appreciated (in Ada, we use tasks, which syntax and
> behavior is defined by the Ada Reference Manual, so the issue about
> portability is left to the compiler/runtime developers).
> 
> 2003-11-19  J. Brobecker  <brobecker@gnat.com>
> 
>         * gdb.threads/pt.c: New file.
>         * gdb.threads/pthread_cond_wait.exp: New test.
> 
> OK to apply?

My only complaint is about pt.c - please use a more descriptive name.
The test itself looks OK.  I would be happier if you didn't play games
with info threads; the order in which GDB will discover threads is
actually somewhat random using gdbserver, since new threads are not
notified.  But this should be OK anyway.

Michael Snyder is the listed maintainer of gdb.threads.  Michael?

> 
> Thanks,
> -- 
> Joel

> /* A small multi-threaded test case.
> 
>    Copyright 2003
>    Free Software Foundation, Inc.
> 
>    This file is part of GDB.
> 
>    This program is free software; you can redistribute it and/or modify
>    it under the terms of the GNU General Public License as published by
>    the Free Software Foundation; either version 2 of the License, or
>    (at your option) any later version.
> 
>    This program is distributed in the hope that it will be useful,
>    but WITHOUT ANY WARRANTY; without even the implied warranty of
>    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
>    GNU General Public License for more details.
> 
>    You should have received a copy of the GNU General Public License
>    along with this program; if not, write to the Free Software
>    Foundation, Inc., 59 Temple Place - Suite 330,
>    Boston, MA 02111-1307, USA.  */
> 
> #include <pthread.h>
> #include <stdio.h>
> #include <time.h>
> 
> void
> cond_wait (pthread_cond_t *cond, pthread_mutex_t *mut)
> {
>   pthread_mutex_lock(mut);
>   pthread_cond_wait (cond, mut);
>   pthread_mutex_unlock (mut);
> }
> 
> void
> noreturn (void)
> {
>   pthread_mutex_t mut;
>   pthread_cond_t cond;
> 
>   pthread_mutex_init (&mut, NULL);
>   pthread_cond_init (&cond, NULL);
> 
>   /* Wait for a condition that will never be signaled, so we effectively
>      block the thread here.  */
>   cond_wait (&cond, &mut);
> }
> 
> void *
> forever_pthread (void *unused)
> {
>   noreturn ();
> }
> 
> void
> break_me (void)
> {
>   /* Just an anchor to help putting a breakpoint.  */
> }
> 
> int
> main (void)
> {
>   pthread_t forever;
>   const struct timespec ts = { 0, 10000000 }; /* 0.01 sec */
> 
>   pthread_create (&forever, NULL, forever_pthread, NULL);
>   for (;;)
>     {
>       nanosleep (&ts, NULL);
>       break_me();
>     }
> 
>   return 0;
> }
> 

> # Copyright (C) 2003 Free Software Foundation, Inc.
> 
> # This program is free software; you can redistribute it and/or modify
> # it under the terms of the GNU General Public License as published by
> # the Free Software Foundation; either version 2 of the License, or
> # (at your option) any later version.
> # 
> # This program is distributed in the hope that it will be useful,
> # but WITHOUT ANY WARRANTY; without even the implied warranty of
> # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
> # GNU General Public License for more details.
> # 
> # You should have received a copy of the GNU General Public License
> # along with this program; if not, write to the Free Software
> # Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.  
> 
> # Please email any bugs, comments, and/or additions to this file to:
> # bug-gdb@gnu.org
> 
> # This file was written by Joel Brobecker.
> #
> # It verifies that GDB is able to compute a backtrace for a thread
> # being blocked on a call to pthread_cond_wait(). 
> 
> if $tracelevel then {
> 	strace $tracelevel
> }
> 
> set testfile "pt"
> set srcfile ${testfile}.c
> set binfile ${objdir}/${subdir}/${testfile}
> 
> if {[gdb_compile_pthreads "${srcdir}/${subdir}/${srcfile}" "${binfile}" executable [list debug "incdir=${objdir}"]] != "" } {
>     return -1
> }
> 
> gdb_exit
> gdb_start
> gdb_reinitialize_dir $srcdir/$subdir
> gdb_load ${binfile}
> 
> gdb_test "break break_me" \
>          "Breakpoint 1 at .*: file .*pt.c, line .*" \
>          "breakpoint on break_me"
> 
> gdb_test "run" \
>          ".*Breakpoint 1, break_me ().*" \
>          "run to break_me"
> 
> # Depending on the thread implementation (Linux Threads, NPTL, etc...),
> # The number of threads known to GDB may vary. We should have at least
> # two threads, but we may have more. We want to switch to the pthread
> # we created via pthread_create, and its ID should be the highest ID
> # of all threads known to GDB.
> set thread_id ""
> send_gdb "info threads\n"
> gdb_expect {
>     -re "\s*(\[0-9\]+) Thread.*$gdb_prompt $" {
>         set thread_id $expect_out(1,string)
>     }
>     default {
>         fail "Unable to find thread id, defaulting to 2"
>         set thread_id "2"
>     }
> }
>     
> 
> # Switch to thread 2, which is doing a forever wait...
> gdb_test "thread $thread_id" \
>          ".*Switching to thread $thread_id.*" \
>          "switching to thread $thread_id"
> 
> # Verify that we are able to get a sensible backtrace, including
> # the frame for the pthread_cond_wait() call.
> gdb_test "backtrace" \
>          ".*pthread_cond_wait.*cond_wait.*noreturn.*forever_pthread.*" \
>          "backtrace in blocked thread"
> 


-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  parent reply	other threads:[~2004-03-05  3:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-20  7:35 Joel Brobecker
2004-02-23 23:33 ` Joel Brobecker
2004-03-05  3:39 ` Daniel Jacobowitz [this message]
2004-03-19  0:09   ` Daniel Jacobowitz
2004-04-13  5:44   ` Joel Brobecker

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=20040305033910.GE5320@nevyn.them.org \
    --to=drow@false.org \
    --cc=brobecker@gnat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=msnyder@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