summaryrefslogtreecommitdiff
path: root/gdb/doc
diff options
context:
space:
mode:
authorDaniel Jacobowitz <dan@debian.org>2009-11-25 20:43:28 +0000
committerDaniel Jacobowitz <dan@debian.org>2009-11-25 20:43:28 +0000
commita550e1ac51b0b7b8ef007f1b91c832e42f4fe653 (patch)
treed137d7754e9831119e102f0931feddd7d3d7c3a2 /gdb/doc
parentc33426511d186177d3e2560a34ef22ae6c661e55 (diff)
downloadgdb-a550e1ac51b0b7b8ef007f1b91c832e42f4fe653.tar.gz
PR gdb/8704
* breakpoint.c (find_condition_and_thread): Correct task error message. * c-exp.y (yylex): Stop before "thread N", "task N", or abbreviations of those. doc/ * gdb.texinfo (Thread-Specific Breakpoints): Thread specifiers are allowed after the breakpoint condition. testsuite/ * gdb.base/condbreak.exp: Test combinations of "break *EXP", "if", and "thread". Correct matching in the previous test.
Diffstat (limited to 'gdb/doc')
-rw-r--r--gdb/doc/ChangeLog7
-rw-r--r--gdb/doc/gdb.texinfo4
2 files changed, 9 insertions, 2 deletions
diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog
index 8571bc9aebc..7c1512412c1 100644
--- a/gdb/doc/ChangeLog
+++ b/gdb/doc/ChangeLog
@@ -1,3 +1,10 @@
+2009-11-24 Daniel Jacobowitz <dan@codesourcery.com>
+
+ PR gdb/8704
+
+ * gdb.texinfo (Thread-Specific Breakpoints): Thread specifiers
+ are allowed after the breakpoint condition.
+
2009-11-23 Tom Tromey <tromey@redhat.com>
PR python/10782:
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index c1ccfc7826e..74cbedffef6 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -5214,8 +5214,8 @@ breakpoint, the breakpoint applies to @emph{all} threads of your
program.
You can use the @code{thread} qualifier on conditional breakpoints as
-well; in this case, place @samp{thread @var{threadno}} before the
-breakpoint condition, like this:
+well; in this case, place @samp{thread @var{threadno}} before or
+after the breakpoint condition, like this:
@smallexample
(@value{GDBP}) break frik.c:13 thread 28 if bartab > lim