From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26049 invoked by alias); 4 Jun 2019 09:38:40 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 25984 invoked by uid 89); 4 Jun 2019 09:38:40 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-6.9 required=5.0 tests=AWL,BAYES_00,HTML_MESSAGE autolearn=ham version=3.3.1 spammy=HTo:U*gdb, H*Ad:U*gdb, H*c:alternative, H*c:HHH X-HELO: mga02.intel.com Received: from mga02.intel.com (HELO mga02.intel.com) (134.134.136.20) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 04 Jun 2019 09:38:37 +0000 Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by orsmga101.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 04 Jun 2019 02:38:35 -0700 Received: from fmsmsx106.amr.corp.intel.com ([10.18.124.204]) by fmsmga001.fm.intel.com with ESMTP; 04 Jun 2019 02:38:35 -0700 Received: from fmsmsx156.amr.corp.intel.com (10.18.116.74) by FMSMSX106.amr.corp.intel.com (10.18.124.204) with Microsoft SMTP Server (TLS) id 14.3.408.0; Tue, 4 Jun 2019 02:38:35 -0700 Received: from shsmsx101.ccr.corp.intel.com (10.239.4.153) by fmsmsx156.amr.corp.intel.com (10.18.116.74) with Microsoft SMTP Server (TLS) id 14.3.408.0; Tue, 4 Jun 2019 02:38:34 -0700 Received: from shsmsx104.ccr.corp.intel.com ([169.254.5.137]) by SHSMSX101.ccr.corp.intel.com ([169.254.1.10]) with mapi id 14.03.0415.000; Tue, 4 Jun 2019 17:38:33 +0800 From: "Xiang, Jing" To: "gdb@sourceware.org" Subject: stop all threads when step over breakpoint and doesn't resume automatically Date: Tue, 04 Jun 2019 09:38:00 -0000 Message-ID: <14F6A9900709CD4B82EAE375B2FCF68552FF0030@SHSMSX104.ccr.corp.intel.com> MIME-Version: 1.0 Return-Path: jing.xiang@intel.com Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes X-SW-Source: 2019-06/txt/msg00002.txt.bz2 Hello, I'm an Firmware developer and meet some problem after upgrade host side GDB= tool from 7.7 version to 8.2.1. There's an GDB stub implemented in our fir= mware and it works well with GDB 7.7. Recently we upgraded gdb.exe to 8.2.1= and met some problem when step over a breakpoint. Our firmware is multithread system, and the GDB stub is implemented over a = specific driver, so it's using non-stop mode to exchange messages between o= ur stub and GDB.exe. With old GDB 7.7, after stop @ a breakpoint and run "= next", it would stop smoothly at next line of the code and other threads st= ill in running state. While with GDB 8.2.1, same steps, after run "next" command at a breakpoint,= it would stop all threads instead. Note: if disable that breakpoint, it would not stop other threads and just = stop at next line of the thread being debugged. Is this expected behavior with GDB 8.2.1? The problem here is that after st= op all threads, it doesn't resume them automatically. Or anything need to b= e changed in our stub to not stop other threads or resume them automaticall= y? Please let me know if any more info needed or how to check it further. Best Regards Jing