From c6e116f53745c48729b3696c005c292f1fd701d7 Mon Sep 17 00:00:00 2001 From: Johannes Sixt Date: Thu, 13 Oct 2011 21:08:19 +0200 Subject: [PATCH] Do not print thread events. Michael Ambrus reported a case where 'info threads' output was contaminated with '[New Thread...]' reports. Normally, these events are reported before the program stops (i.e., while it is running). Work it around by turning off these event reports. --- kdbg/gdbdriver.cpp | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/kdbg/gdbdriver.cpp b/kdbg/gdbdriver.cpp index 19a1370..e5db247 100644 --- a/kdbg/gdbdriver.cpp +++ b/kdbg/gdbdriver.cpp @@ -234,6 +234,11 @@ bool GdbDriver::startup(QString cmdStr) "set print static-members off\n" "set print asm-demangle on\n" /* + * Sometimes, gdb prints [New Thread ...] during 'info threads'; + * we will not look at thread events anyway, so turn them off. + */ + "set print thread-events off\n" + /* * Don't assume that program functions invoked from a watch expression * always succeed. */ -- 2.11.4.GIT