From f4f4330e517a0497601baf6253d6408b77b10626 Mon Sep 17 00:00:00 2001 From: Pedro Alves Date: Thu, 10 Dec 2015 17:47:57 +0000 Subject: [PATCH] [gdb/doc] Explain that there's always a thread This warning is a few years out of date -- there's always a thread nowadays. gdb/doc/ChangeLog: * gdb.texinfo (Threads): Replace warning with explanation about single-threaded programs. --- gdb/doc/ChangeLog | 5 +++++ gdb/doc/gdb.texinfo | 22 ++++------------------ 2 files changed, 9 insertions(+), 18 deletions(-) diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog index 59f1eff7556..fc81d096525 100644 --- a/gdb/doc/ChangeLog +++ b/gdb/doc/ChangeLog @@ -1,3 +1,8 @@ +2015-12-10 Pedro Alves + + * gdb.texinfo (Threads): Replace warning with explanation + about single-threaded programs. + 2015-12-10 Pedro Alves * gdb.texinfo (Threads): Remove mention of SGI. diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo index e8b419c9518..bb68e21baf9 100644 --- a/gdb/doc/gdb.texinfo +++ b/gdb/doc/gdb.texinfo @@ -2844,24 +2844,6 @@ the user specify which @code{libthread_db} to use if the default choice isn't compatible with the program. @end itemize -@quotation -@emph{Warning:} These facilities are not yet available on every -@value{GDBN} configuration where the operating system supports threads. -If your @value{GDBN} does not support threads, these commands have no -effect. For example, a system without thread support shows no output -from @samp{info threads}, and always rejects the @code{thread} command, -like this: - -@smallexample -(@value{GDBP}) info threads -(@value{GDBP}) thread 1 -Thread ID 1 not known. Use the "info threads" command to -see the IDs of currently known threads. -@end smallexample -@c FIXME to implementors: how hard would it be to say "sorry, this GDB -@c doesn't support threads"? -@end quotation - @cindex focus of debugging @cindex current thread The @value{GDBN} thread debugging facility allows you to observe all @@ -2903,6 +2885,10 @@ further qualifier. For debugging purposes, @value{GDBN} associates its own thread number---always a single integer---with each thread in your program. +From @value{GDBN}'s perspective, a process always has at least one +thread. In other words, @value{GDBN} assigns a thread number to the +program's ``main thread'' even if the program is not multi-threaded. + @table @code @kindex info threads @item info threads @r{[}@var{id}@dots{}@r{]} -- 2.30.2