OpenE2K
/
binutils-gdb
12
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Thread-specific breakpoints: say "no longer in the thread list" instead of "gone". 

It seems "gone" may confuse people, while that was exactly what it was
trying to avoid.  Switch to saying "no longer in the thread list",
which is really the predicate GDB uses.

gdb/
2013-10-07  Pedro Alves  <palves@redhat.com>

	PR breakpoints/11568
	* breakpoint.c (remove_threaded_breakpoints): Say "no longer in
	the thread list" instead of "gone".
This commit is contained in:
Pedro Alves 2013-10-07 11:00:23 +00:00
parent 0c5571793a
commit 46ecd52745
2 changed files with 7 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
gdb/ChangeLog
View File

@ -1,3 +1,9 @@
2013-10-07 Pedro Alves <palves@redhat.com>
PR breakpoints/11568
* breakpoint.c (remove_threaded_breakpoints): Say "no longer in
the thread list" instead of "gone".
2013-10-06 Sergio Durigan Junior <sergiodj@redhat.com>
* NEWS: Mention new convenience variable $_exitsignal.

2
gdb/breakpoint.c
View File

@ -2943,7 +2943,7 @@ remove_threaded_breakpoints (struct thread_info *tp, int silent)
b->disposition = disp_del_at_next_stop;
printf_filtered (_("\
Thread-specific breakpoint %d deleted - thread %d is gone.\n"),
Thread-specific breakpoint %d deleted - thread %d no longer in the thread list.\n"),
b->number, tp->num);
/* Hide it from the user. */