This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug breakpoints/15434] Dprintf uses a synchronous 'continue' even in non-stop mode
- From: "marc.khouzam at ericsson dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Mon, 13 May 2013 17:12:53 +0000
- Subject: [Bug breakpoints/15434] Dprintf uses a synchronous 'continue' even in non-stop mode
- Auto-submitted: auto-generated
- References: <bug-15434-4717 at http dot sourceware dot org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=15434
--- Comment #4 from Marc Khouzam <marc.khouzam at ericsson dot com> 2013-05-13 17:12:53 UTC ---
To see the problem, I suggest you do the following:
(gdb) set target-async on
(gdb) set non-stop on
(gdb) r&
Then type:
interrupt
The thread should be interrupted. This is the expected behavior because in
non-stop, you can still talk to GDB when the inferior is running.
The bad behavior is from:
(gdb) set target-async on
(gdb) set non-stop on
(gdb) dprintf 8,"go\n"
(gdb) r&
Then, when you type interrupt, GDB will ignore it because it did a 'continue'
at the dprintf, instead of a 'continue&'. You must then do ^C to get control
back.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.