From: Vladimir Prus <vladimir@codesourcery.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [MI non-stop 10/11] Skip varobj in running threads.
Date: Sun, 13 Jul 2008 05:34:00 -0000 [thread overview]
Message-ID: <g5c44i$b9s$1@ger.gmane.org> (raw)
In-Reply-To: <200806282100.06214.vladimir@codesourcery.com>
[-- Attachment #1: Type: text/plain, Size: 289 bytes --]
Vladimir Prus wrote:
>
> If a variable object is bound to a specific thread, and we're doing
>
> -var-update *
>
> and varobj's thread is running, we cannot update varobj -- so we skip it.
> Will commit when core non-stop is in.
I've checked in the following revision.
- Volodya
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: commit.diff --]
[-- Type: text/x-diff; name="commit.diff", Size: 2832 bytes --]
Index: gdb/ChangeLog
===================================================================
RCS file: /cvs/src/src/gdb/ChangeLog,v
retrieving revision 1.9558
diff -u -p -r1.9558 ChangeLog
--- gdb/ChangeLog 13 Jul 2008 04:13:49 -0000 1.9558
+++ gdb/ChangeLog 13 Jul 2008 05:29:56 -0000
@@ -1,5 +1,12 @@
2008-07-13 Vladimir Prus <vladimir@codesourcery.com>
+ Skip varobj in running threads.
+ * mi/mi-cmd-var.c (mi_cmd_var_update): If varobj's
+ thread is not stopped, skip the varobj.
+ * Makefile.in: Update dependencies.
+
+2008-07-13 Vladimir Prus <vladimir@codesourcery.com>
+
Enable all commands while inferiour is running
* mi/mi-main.c (mi_cmd_execute): Don't check if
inferiour is executing.
Index: gdb/Makefile.in
===================================================================
RCS file: /cvs/src/src/gdb/Makefile.in,v
retrieving revision 1.1036
diff -u -p -r1.1036 Makefile.in
--- gdb/Makefile.in 12 Jul 2008 22:16:34 -0000 1.1036
+++ gdb/Makefile.in 13 Jul 2008 05:29:58 -0000
@@ -3256,7 +3256,8 @@ mi-cmd-target.o: $(srcdir)/mi/mi-cmd-tar
$(mi_getopt_h) $(remote_h)
$(CC) -c $(INTERNAL_CFLAGS) $(srcdir)/mi/mi-cmd-target.c
mi-cmd-var.o: $(srcdir)/mi/mi-cmd-var.c $(defs_h) $(mi_cmds_h) $(ui_out_h) \
- $(mi_out_h) $(varobj_h) $(value_h) $(gdb_string_h) $(mi_getopt_h)
+ $(mi_out_h) $(varobj_h) $(value_h) $(gdb_string_h) $(mi_getopt_h) \
+ $(gdbthread_h)
$(CC) -c $(INTERNAL_CFLAGS) $(srcdir)/mi/mi-cmd-var.c
mi-console.o: $(srcdir)/mi/mi-console.c $(defs_h) $(mi_console_h) \
$(gdb_string_h)
Index: gdb/mi/mi-cmd-var.c
===================================================================
RCS file: /cvs/src/src/gdb/mi/mi-cmd-var.c,v
retrieving revision 1.52
diff -u -p -r1.52 mi-cmd-var.c
--- gdb/mi/mi-cmd-var.c 25 Jun 2008 15:15:42 -0000 1.52
+++ gdb/mi/mi-cmd-var.c 13 Jul 2008 05:30:17 -0000
@@ -29,6 +29,7 @@
#include <ctype.h>
#include "gdb_string.h"
#include "mi-getopt.h"
+#include "gdbthread.h"
const char mi_no_values[] = "--no-values";
const char mi_simple_values[] = "--simple-values";
@@ -610,8 +611,21 @@ mi_cmd_var_update (char *command, char *
cr = rootlist;
while (*cr != NULL)
{
- if (*name == '*' || varobj_floating_p (*cr))
- varobj_update_one (*cr, print_values, 0 /* implicit */);
+ int thread_id = varobj_get_thread_id (*cr);
+ int thread_stopped = 0;
+ if (thread_id == -1 && is_stopped (inferior_ptid))
+ thread_stopped = 1;
+ else
+ {
+ struct thread_info *tp = find_thread_id (thread_id);
+ if (tp)
+ thread_stopped = is_stopped (tp->ptid);
+ else
+ thread_stopped = 1;
+ }
+ if (thread_stopped)
+ if (*name == '*' || varobj_floating_p (*cr))
+ varobj_update_one (*cr, print_values, 0 /* implicit */);
cr++;
}
do_cleanups (cleanup);
prev parent reply other threads:[~2008-07-13 5:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-28 17:22 Vladimir Prus
2008-07-11 13:53 ` Daniel Jacobowitz
2008-07-11 19:07 ` Vladimir Prus
2008-07-11 13:57 ` Pedro Alves
2008-07-11 14:02 ` Daniel Jacobowitz
2008-07-13 5:34 ` Vladimir Prus [this message]
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='g5c44i$b9s$1@ger.gmane.org' \
--to=vladimir@codesourcery.com \
--cc=gdb-patches@sources.redhat.com \
/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