From: Yao Qi <yao@codesourcery.com>
To: Muhammad Waqas <mwaqas@codesourcery.com>
Cc: <gdb-patches@sourceware.org>, <tromey@redhat.com>,
<ali_anwar@codesourcery.com>
Subject: Re: [PATCH with testcase] Bug 11568 - delete thread-specific breakpoint on the thread exit
Date: Mon, 29 Jul 2013 14:18:00 -0000 [thread overview]
Message-ID: <51F67992.30704@codesourcery.com> (raw)
In-Reply-To: <51F65519.2080806@codesourcery.com>
On 07/29/2013 07:42 PM, Muhammad Waqas wrote:
Please have a look at
http://sourceware.org/gdb/wiki/ContributionChecklist , it is very
helpful for you to avoid some issues in your patch.
> 2013-07-24 Muhammad Waqas<mwaqas@codesourcery.com>
^^^ Two spaces.
>
> PR gdb/11568
> * breakpoint.c (breakpoint_auto_delete): add new condition
> Remove thread related breakpoints if threads are exited.
^^^^^^^ Tab instead of spaces.
The changelog entry is like this:
PR gdb/11568
* breakpoint.c (breakpoint_auto_delete): Remove thread related
breakpoints if threads are exited.
>
>
>
> Index: ./gdb/breakpoint.c
> ===================================================================
> RCS file: /cvs/src/src/gdb/breakpoint.c,v
> retrieving revision 1.772
> diff -u -p -r1.772 breakpoint.c
> --- ./gdb/breakpoint.c 6 Jul 2013 07:14:54 -0000 1.772
> +++ ./gdb/breakpoint.c 29 Jul 2013 11:22:05 -0000
> @@ -11910,6 +11910,15 @@ breakpoint_auto_delete (bpstat bs)
> {
> if (b->disposition == disp_del_at_next_stop)
> delete_breakpoint (b);
> + else if (b->thread > 0) /* If breakpoint relates to user created
> + thread Check if it's not alive then
> + delete it*/
Please move the comments into the brackets below. Period is missing in
your comment, and we need two spaces after period at the end of comment.
> + {
> + struct thread_info * tp = find_thread_id (b->thread) ;
A blank line is needed here. Indentation looks wrong here.
> + if (tp != NULL && (tp->state == THREAD_EXITED
> + || !target_thread_alive (tp->ptid)))
> + delete_breakpoint (b);
and here.
> + }
> }
> }
>
I run thread-specific-bp.exp in async/non-stop mode, and I get a fail.
I am afraid your patch only works in all-stop mode.
>
> testsuite/Changlog
>
> 2013-07-29 Muhammad Waqas<mwaqas@codesourcery.com>
> Jan Kratochvil<jan.kratochvil@redhat.com>
^^^^^^^^^^
Need a tab instead of spaces. Please reference existing entries in
ChangeLog to see how to list two authors.
>
> * gdb.threads/thread-specific-bp.c: New file.
> * gdb.threads/thread-specific-bp.exp: New file.
Please include these new added files into your patch, so that people can
review them. Here is an example
(http://sourceware.org/ml/gdb-patches/2013-07/msg00671.html) I include
new added file in the patch. I use git, but you can get the similar
patch in cvs.
> # Copyright (C) 1996-2013 Free Software Foundation, Inc.
It should be 2013 only.
> gdb_test_multiple "info breakpoint" "get info" {
> -re "(\[0-9\]+)(\[^\n\r\]*breakpoint\[^\n\r\]*main.*thread $thre)" {
I don't really understand this pattern. Probably, we only want to match
"thread $thre"
".*$gdb_prompt $" is missing at the end of the pattern. Please add it.
> fail "threaded breakpoint not deleted"
> }
> -re "(\[0-9\]+)(\[^\n\r\]*breakpoint\[^\n\r\]*main.*\n)" {
> pass "threaded breakpoint deleted"
fail/pass should be the same.
> }
> }
Something like this:
set test "thread-specific breakpoint is deleted"
gdb_test_multiple "info breakpoint" $test {
-re "thread $thre.*$gdb_prompt $" {
fail $test
}
-re "$gdb_prompt $" {
pass $test
}
}
There are some trailing spaces in the test. Please remove them.
--
Yao (é½å°§)
next prev parent reply other threads:[~2013-07-29 14:18 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-29 7:29 Muhammad Waqas
2013-07-29 9:21 ` Yao Qi
2013-07-29 11:42 ` Muhammad Waqas
2013-07-29 14:18 ` Yao Qi [this message]
2013-07-30 10:34 ` Muhammad Waqas
2013-07-31 2:41 ` Yao Qi
2013-08-01 10:51 ` Pedro Alves
2013-08-01 10:59 ` Yao Qi
2013-08-01 11:27 ` Pedro Alves
2013-08-01 12:10 ` Yao Qi
2013-08-01 11:57 ` Pedro Alves
2013-08-01 12:44 ` Muhammad Waqas
2013-08-02 9:45 ` Pedro Alves
2013-08-05 12:01 ` Muhammad Waqas
2013-08-05 13:57 ` Tom Tromey
2013-08-06 6:12 ` Muhammad Waqas
2013-08-22 9:42 ` Muhammad Waqas
2013-08-22 17:14 ` Pedro Alves
2013-08-23 5:31 ` Muhammad Waqas
2013-08-27 11:31 ` Muhammad Waqas
2013-08-27 19:02 ` Pedro Alves
2013-08-27 19:06 ` Pedro Alves
2013-08-28 12:26 ` Muhammad Waqas
2013-08-30 16:28 ` Pedro Alves
2013-09-02 4:06 ` Muhammad Waqas
2013-09-02 8:39 ` Pedro Alves
2013-09-02 9:46 ` Muhammad Waqas
2013-09-02 10:24 ` Pedro Alves
2013-09-02 10:32 ` Muhammad Waqas
2013-09-02 10:48 ` Pedro Alves
2013-09-02 16:46 ` Pedro Alves
2013-09-02 16:52 ` [PATCH] PR gdb/11568 - delete thread-specific breakpoints on " Pedro Alves
2013-09-09 16:07 ` Tom Tromey
2013-09-17 19:36 ` Pedro Alves
2013-09-19 14:48 ` [COMMIT PATCH] Fix regressions caused by thread-specific breakpoint deletion. (was: Re: [PATCH] PR gdb/11568 - delete thread-specific breakpoints on thread exit) Pedro Alves
2013-08-28 12:26 ` [PATCH with testcase] Bug 11568 - delete thread-specific breakpoint on the thread exit Muhammad Waqas
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=51F67992.30704@codesourcery.com \
--to=yao@codesourcery.com \
--cc=ali_anwar@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=mwaqas@codesourcery.com \
--cc=tromey@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