From: Jeff Johnston <jjohnstn@redhat.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch] New thread test to exercise Daniel's Patch
Date: Mon, 29 Mar 2004 21:59:00 -0000 [thread overview]
Message-ID: <40689C42.4090901@redhat.com> (raw)
In-Reply-To: <20040329213444.GA32070@nevyn.them.org>
[-- Attachment #1: Type: text/plain, Size: 536 bytes --]
Daniel Jacobowitz wrote:
> On Mon, Mar 29, 2004 at 04:04:00PM -0500, Jeff Johnston wrote:
>
>>Ok, I had the thread checks in the Continue test. If I change it to the
>>way above, now I get 3 "Process no longer exists "messages but the test
>>completes. :(
>>
>>I'm really starting to hate these test macros. What is the reasoning
>>behind avoiding send_gdb / gdb_expect?
>
>
> They don't automatically handle things like internal errors,
> disconnects, et cetera. Want to post your current version and I'll
> give it a try?
>
[-- Attachment #2: manythreads.c --]
[-- Type: text/plain, Size: 664 bytes --]
#include <pthread.h>
#include <stdio.h>
void *
thread_function (void *arg)
{
int x = (int)arg;
printf ("Thread <%d> executing\n", x);
return NULL;
}
int
main (int argc, char **argv)
{
pthread_attr_t attr;
pthread_t threads[256];
int i, j;
pthread_attr_init (&attr);
/* Create a ton of quick-executing threads, then wait for them to
complete. */
for (i = 0; i < 1000; ++i)
{
for (j = 0; j < 256; ++j)
{
pthread_create (&threads[j], &attr, thread_function,
(void *)(i * 1000 + j));
}
for (j = 0; j < 256; ++j)
{
pthread_join (threads[j], NULL);
}
}
pthread_attr_destroy (&attr);
return 0;
}
[-- Attachment #3: manythreads.exp --]
[-- Type: text/plain, Size: 3495 bytes --]
# manythreads.exp -- Expect script to test stopping many threads
# Copyright (C) 2004 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@prep.ai.mit.edu
# This file was written by Jeff Johnston. (jjohnstn@redhat.com)
if $tracelevel then {
strace $tracelevel
}
set prms_id 0
set bug_id 0
set testfile "manythreads"
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_start
gdb_reinitialize_dir $srcdir/$subdir
gdb_load ${binfile}
gdb_test "set print sevenbit-strings" ""
runto_main
# We'll need this when we send_gdb a ^C to GDB. Need to do it before we
# run the program and gdb starts saving and restoring tty states.
# On Ultrix, we don't need it and it is really slow (because shell_escape
# doesn't use vfork).
if ![istarget "*-*-ultrix*"] then {
gdb_test "shell stty intr '^C'" ""
}
gdb_test_multiple "continue" "first continue" {
-re "ERROR:.*$gdb_prompt $" {
fail "$message"
}
-re "Continuing" {
pass "$message"
}
}
# Send a Ctrl-C and verify that we can do info threads and continue
after 1000 {send_gdb "\003"}
gdb_test_multiple "" "stop threads 1" {
-re "\\\[New thread \[^\]\]*\\\]\r\n" {
exp_continue
}
-re "\\\[Thread \[^\]\]* exited\\\]\r\n" {
exp_continue
}
-re "Thread.*executing\r\n" {
exp_continue
}
-re "Program received signal SIGINT.*$gdb_prompt $"
{
pass "$message"
}
timeout
{
fail "$message (timeout)"
}
}
gdb_test "info threads" ".*1 Thread.*.LWP.*"
gdb_test_multiple "continue" "second continue" {
-re "ERROR:.*$gdb_prompt $" {
fail "$message"
}
-re "Continuing" {
pass "$message"
}
}
# Send another Ctrl-C and verify that we can do info threads and quit
after 1000 {send_gdb "\003"}
gdb_test_multiple "" "stop threads 2" {
-re "\\\[New thread \[^\]\]*\\\]\r\n" {
exp_continue
}
-re "\\\[Thread \[^\]\]* exited\\\]\r\n" {
exp_continue
}
-re "Thread.*executing\r\n" {
exp_continue
}
-re "Program received signal SIGINT.*$gdb_prompt $"
{
pass "stop threads 2"
}
timeout
{
fail "stop threads 2 (timeout)"
}
}
gdb_test_multiple "quit" "GDB exits after stopping multithreaded program" {
-re "The program is running. Exit anyway\\? \\(y or n\\) $" {
gdb_test_multiple "y" "$message" {
eof {
pass "GDB exits after stopping multithreaded program"
}
}
}
eof {
pass "GDB exits after stopping multithreaded program"
}
timeout {
fail "GDB exits after stopping multithreaded program (timeout)"
}
}
next prev parent reply other threads:[~2004-03-29 21:59 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-19 0:36 [RFC]: fix for recycled thread ids Jeff Johnston
2004-03-19 1:53 ` Daniel Jacobowitz
2004-03-19 18:44 ` Jeff Johnston
2004-03-19 19:01 ` Daniel Jacobowitz
2004-03-19 19:35 ` Jeff Johnston
2004-03-19 19:40 ` Daniel Jacobowitz
2004-03-19 21:32 ` Jeff Johnston
2004-03-24 15:51 ` Daniel Jacobowitz
2004-03-24 16:56 ` Daniel Jacobowitz
2004-03-24 21:56 ` Jeff Johnston
2004-03-25 0:46 ` Jeff Johnston
2004-03-25 4:39 ` Daniel Jacobowitz
2004-03-25 16:34 ` Daniel Jacobowitz
2004-03-25 20:22 ` Jeff Johnston
2004-03-26 17:59 ` [patch] Use TD_DEATH and PTRACE_EVENT_CLONE when available (was: Re: [RFC]: fix for recycled thread ids) Daniel Jacobowitz
2004-03-26 18:14 ` [patch] Use TD_DEATH and PTRACE_EVENT_CLONE when available Jeff Johnston
2004-03-26 21:13 ` [patch] New thread test to exercise Daniel's Patch Jeff Johnston
2004-03-26 21:19 ` Daniel Jacobowitz
2004-03-29 18:06 ` Jeff Johnston
2004-03-29 18:11 ` Daniel Jacobowitz
2004-03-29 20:18 ` Jeff Johnston
2004-03-29 20:42 ` Daniel Jacobowitz
2004-03-29 21:04 ` Jeff Johnston
2004-03-29 21:34 ` Daniel Jacobowitz
2004-03-29 21:59 ` Jeff Johnston [this message]
2004-03-29 22:32 ` Daniel Jacobowitz
2004-03-29 22:58 ` Jeff Johnston
2004-03-29 23:57 ` Daniel Jacobowitz
2004-03-29 18:07 ` [patch] Use TD_DEATH and PTRACE_EVENT_CLONE when available (was: Re: [RFC]: fix for recycled thread ids) Daniel Jacobowitz
2004-03-19 20:33 ` [RFC]: fix for recycled thread ids Andrew Cagney
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=40689C42.4090901@redhat.com \
--to=jjohnstn@redhat.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