From: "Xiang, Jing" <jing.xiang@intel.com>
To: "gdb@sourceware.org" <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 [thread overview]
Message-ID: <14F6A9900709CD4B82EAE375B2FCF68552FF0030@SHSMSX104.ccr.corp.intel.com> (raw)
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 firmware 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 our 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 still 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 stop all threads, it doesn't resume them automatically. Or anything need to be changed in our stub to not stop other threads or resume them automatically? Please let me know if any more info needed or how to check it further.
Best Regards
Jing
reply other threads:[~2019-06-04 9:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=14F6A9900709CD4B82EAE375B2FCF68552FF0030@SHSMSX104.ccr.corp.intel.com \
--to=jing.xiang@intel.com \
--cc=gdb@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).