public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Amos Bird <amosbird@gmail.com>
To: Gary Benson <gbenson@redhat.com>
Cc: Eli Zaretskii <eliz@gnu.org>, gdb-patches@sourceware.org, tom@tromey.com
Subject: Re: [PATCH] Add "thread-exited" annotation
Date: Fri, 17 May 2019 10:55:00 -0000	[thread overview]
Message-ID: <87sgtdcpux.fsf@gmail.com> (raw)
In-Reply-To: <20190517095941.GA2356@blade.nx>



> Also, Amos, do you have copyright assignment in place?
Yup, it's all set.

Gary Benson <gbenson@redhat.com> writes:

> Amos Bird wrote:
>> Thanks. Updated.
>
> Cool.  I'm happy for this to be committed now, but I'm not a
> maintainer so I can't approve it.
>
> Also, Amos, do you have copyright assignment in place?
>
> Thanks,
> Gary
>
>> Eli Zaretskii <eliz@gnu.org> writes:
>>
>> >>From: Amos Bird <amosbird@gmail.com>
>> >>Cc: gdb-patches@sourceware.org, Tom Tromey <tom@tromey.com>
>> >>Date: Thu, 16 May 2019 22:10:14 +0800
>> >>
>> >>+* 'thread-exited' event is now available in the annotations
>> >>interface
>> >
>> >A period at the end of the sentence is missing.
>> >
>> >>+This annotation is issued once for each thread that is 
>> >>exited.
>> >                                      ^^^^^^^^^^^^^^^^^^^^^^^^^^
>> >"each thread that exits"
>> >
>> >The documentation parts are OK with these 2 nits fixed.
>> >
>> >Thanks.
>>
>>
>> --
>> Amos Bird
>> amosbird@gmail.com
>
>> From b6dc912764a0e61e274b9354ca225af4a235a3dd Mon Sep 17 
>> 00:00:00 2001
>> From: Amos Bird <amosbird@gmail.com>
>> Date: Thu, 16 May 2019 22:44:40 +0800
>> Subject: [PATCH] Add "thread-exit" annotation.
>>
>> ---
>>  gdb/ChangeLog                      |  5 +++++
>>  gdb/NEWS                           |  2 ++
>>  gdb/annotate.c                     | 14 ++++++++++++++
>>  gdb/doc/ChangeLog                  |  5 +++++
>>  gdb/doc/annotate.texinfo           |  5 +++++
>>  gdb/testsuite/ChangeLog            |  5 +++++
>>  gdb/testsuite/gdb.base/annota1.exp |  9 +++++++++
>>  7 files changed, 45 insertions(+)
>>
>> diff --git a/gdb/ChangeLog b/gdb/ChangeLog
>> index e0120e7743..849ed30731 100644
>> --- a/gdb/ChangeLog
>> +++ b/gdb/ChangeLog
>> @@ -1,3 +1,8 @@
>> +2019-04-26  Amos Bird  <amosbird@gmail.com>
>> +
>> +	* annotate.c (annotate_thread_exited): Add "thread-exited"
>> +	annotation.
>> +
>>  2019-04-25  Keith Seitz  <keiths@redhat.com>
>>
>>  	PR c++/24367
>> diff --git a/gdb/NEWS b/gdb/NEWS
>> index 5309a8f923..735d915ec6 100644
>> --- a/gdb/NEWS
>> +++ b/gdb/NEWS
>> @@ -3,6 +3,8 @@
>>
>>  *** Changes since GDB 8.3
>>
>> +* 'thread-exited' event is now available in the annotations 
>> interface.
>> +
>>  * New built-in convenience variables $_gdb_major and 
>>  $_gdb_minor
>>    provide the GDB version.  They are handy for conditionally 
>>    using
>>    features available only in or since specific GDB versions, 
>>    in
>> diff --git a/gdb/annotate.c b/gdb/annotate.c
>> index 97cb4c8855..af804ddd1f 100644
>> --- a/gdb/annotate.c
>> +++ b/gdb/annotate.c
>> @@ -241,6 +241,19 @@ annotate_thread_changed (void)
>>      }
>>  }
>>
>> +/* Emit notification on thread exit.  */
>> +
>> +static void
>> +annotate_thread_exited (struct thread_info *t, int silent)
>> +{
>> +  if (annotation_level > 1)
>> +    {
>> +      printf_filtered(("\n\032\032thread-exited,"
>> +                       "id=\"%d\",group-id=\"i%d\"\n"),
>> +                      t->global_num, t->inf->num);
>> +    }
>> +}
>> +
>>  void
>>  annotate_field_begin (struct type *type)
>>  {
>> @@ -595,4 +608,5 @@ _initialize_annotate (void)
>>    gdb::observers::breakpoint_created.attach 
>>    (breakpoint_changed);
>>    gdb::observers::breakpoint_deleted.attach 
>>    (breakpoint_changed);
>>    gdb::observers::breakpoint_modified.attach 
>>    (breakpoint_changed);
>> +  gdb::observers::thread_exit.attach (annotate_thread_exited);
>>  }
>> diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog
>> index ba152329d7..79b837aac6 100644
>> --- a/gdb/doc/ChangeLog
>> +++ b/gdb/doc/ChangeLog
>> @@ -1,3 +1,8 @@
>> +2019-04-26  Amos Bird  <amosbird@gmail.com>
>> +
>> +	* annotate.texinfo (Multi-threaded Apps): Add entry for 
>> thread-exited
>> +	annotation.
>> +
>>  2019-04-22  Pedro Alves  <palves@redhat.com>
>>
>>  	* gdb.texinfo (Reverse Execution): Mention and xref 
>>  process record
>> diff --git a/gdb/doc/annotate.texinfo 
>> b/gdb/doc/annotate.texinfo
>> index b85b759f9a..fb7cbf7b77 100644
>> --- a/gdb/doc/annotate.texinfo
>> +++ b/gdb/doc/annotate.texinfo
>> @@ -836,6 +836,11 @@ The selected thread has changed.  This may 
>> occur at the request of the
>>  user with the @code{thread} command, or as a result of 
>>  execution,
>>  e.g., another thread hits a breakpoint.
>>
>> +@findex thread-exited@r{, annotation}
>> +@item ^Z^Zthread-exited
>> +
>> +This annotation is issued once for each thread that exits.
>> +
>>  @end table
>>
>>  @node GNU Free Documentation License
>> diff --git a/gdb/testsuite/ChangeLog b/gdb/testsuite/ChangeLog
>> index 9b0725a033..d7a9b5611d 100644
>> --- a/gdb/testsuite/ChangeLog
>> +++ b/gdb/testsuite/ChangeLog
>> @@ -1,3 +1,8 @@
>> +2019-04-26  Amos Bird  <amosbird@gmail.com>
>> +
>> +	* gdb.base/annota1.exp (thread_switch): Add test for
>> +	thread-exited annotation.
>> +
>>  2019-04-25  Keith Seitz  <keiths@redhat.com>
>>
>>  	PR c++/24367
>> diff --git a/gdb/testsuite/gdb.base/annota1.exp 
>> b/gdb/testsuite/gdb.base/annota1.exp
>> index 5237bc9715..032cd2ecde 100644
>> --- a/gdb/testsuite/gdb.base/annota1.exp
>> +++ b/gdb/testsuite/gdb.base/annota1.exp
>> @@ -492,8 +492,17 @@ proc thread_switch {} {
>>      }
>>  }
>>
>> +proc thread_exit {} {
>> +    gdb_test_multiple "call (void)pthread_exit()" "thread 
>> exit" {
>> +	-re ".*\032\032thread-exited.*" {
>> +	    pass "thread exit"
>> +	}
>> +    }
>> +}
>> +
>>  thread_test
>>  thread_switch
>> +thread_exit
>>
>>  # restore the original prompt for the rest of the testsuite
>>
>> --
>> 2.21.0
>>


--
Amos Bird
amosbird@gmail.com

  reply	other threads:[~2019-05-17 10:55 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-26 15:19 Amos Bird
2019-04-30 15:45 ` Tom Tromey
2019-04-30 17:09   ` Amos Bird
2019-05-16 13:14     ` Gary Benson
2019-05-16 14:10       ` Amos Bird
2019-05-16 14:35         ` Eli Zaretskii
2019-05-16 14:45           ` Amos Bird
2019-05-17  9:59             ` Gary Benson
2019-05-17 10:55               ` Amos Bird [this message]
2019-05-17 13:08             ` Simon Marchi
2019-05-17 13:23               ` Amos Bird
2019-05-17 14:22                 ` Simon Marchi
2019-05-17 15:50                   ` Amos Bird
2019-05-17 16:26                     ` Pedro Alves
2019-05-17 17:13                       ` Amos Bird
2019-06-06 15:37                         ` Amos Bird
2019-06-06 16:32                         ` Pedro Alves
2019-06-06 17:11                           ` Amos Bird
2019-06-06 17:37                             ` Tom Tromey

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=87sgtdcpux.fsf@gmail.com \
    --to=amosbird@gmail.com \
    --cc=eliz@gnu.org \
    --cc=gbenson@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tom@tromey.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).