This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Don't warn if target reports no threads
- From: Vladimir Prus <vladimir at codesourcery dot com>
- To: gdb-patches at sourceware dot org
- Date: Tue, 19 Oct 2010 18:52:03 +0400
- Subject: Don't warn if target reports no threads
In the case when stub refuses to understand all modern thread-listing packets,
GDB falls back to qL packet, if if stub refuses to handle that either,
reports:
RMT ERROR : failed to get remote thread list.
The further operation continues normally, and qL is really optional packet, so
there's no point scaring a user like that. Is the patch below OK?
- Volodya
diff --git a/gdb/remote.c b/gdb/remote.c
index 50e671d..e3c4117 100644
--- a/gdb/remote.c
+++ b/gdb/remote.c
@@ -2523,7 +2523,6 @@ remote_get_threadlist (int startflag, threadref *nextthread, int result_limit,
{
if (*done != 1)
{
- warning (_("RMT ERROR : failed to get remote thread list."));
result = 0;
}
return result; /* break; */