From: Jeff Johnston <jjohnstn@redhat.com>
To: Michael Snyder <msnyder@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA]: New test for gdb.threads testsuite
Date: Thu, 22 Apr 2004 22:20:00 -0000 [thread overview]
Message-ID: <4088451F.1090702@redhat.com> (raw)
In-Reply-To: <40883E43.6010200@redhat.com>
Michael Snyder wrote:
> Jeff Johnston wrote:
>
>> The attached testcase tests the new code added recently by Daniel.
>>
>> Ok to commit?
>>
>> -- Jeff J.
>>
>> 2004-03-29 Jeff Johnston <jjohnstn@redhat.com>
>> Daniel Jacobowitz <drow@mvista.com>
>>
>> * gdb.threads/manythreads.c: New testcase.
>> * gdb.threads/manythreads.exp: Ditto.
>
>
> Looks good to me, Jeff. Please check it in.
> Michael
>
Done. Thanks.
-- Jeff J.
>> ------------------------------------------------------------------------
>>
>> #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;
>> }
>>
>>
>> ------------------------------------------------------------------------
>>
>> # 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'" ""
>> }
>>
>> set message "first continue"
>> 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"}
>> set message "stop threads 1"
>> gdb_test_multiple "" "stop threads 1" {
>> -re "\\\[New \[^\]\]*\\\]\r\n" {
>> exp_continue
>> }
>> -re "\\\[\[^\]\]* exited\\\]\r\n" {
>> exp_continue
>> }
>> -re "Thread \[^\n\]* 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.*"
>>
>> set message "second continue"
>> 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"}
>> set message "stop threads 2"
>> gdb_test_multiple "" "stop threads 2" {
>> -re "\\\[New \[^\]\]*\\\]\r\n" {
>> exp_continue
>> }
>> -re "\\\[\[^\]\]* exited\\\]\r\n" {
>> exp_continue
>> }
>> -re "Thread \[^\n\]* executing\r\n" {
>> exp_continue
>> }
>> -re "Program received signal SIGINT.*$gdb_prompt $" {
>> pass "stop threads 2"
>> }
>> }
>> gdb_test_multiple "quit" "GDB exits after stopping multithreaded
>> program" {
>> -re "The program is running. Exit anyway\\? \\(y or n\\) $" {
>> send_gdb "y\n"
>> exp_continue
>> }
>> eof {
>> pass "GDB exits after stopping multithreaded program"
>> }
>> timeout {
>> fail "GDB exits after stopping multithreaded program (timeout)"
>> }
>> }
>>
>
>
>
next prev parent reply other threads:[~2004-04-22 22:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-30 0:22 Jeff Johnston
2004-04-12 21:05 ` Jeff Johnston
2004-04-22 21:51 ` Michael Snyder
2004-04-22 22:20 ` Jeff Johnston [this message]
2004-04-22 22:49 Michael Elizabeth Chastain
2004-04-23 16:06 ` Jeff Johnston
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=4088451F.1090702@redhat.com \
--to=jjohnstn@redhat.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