Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Hui Zhu <teawater@gmail.com>
To: Stan Shebs <stanshebs@earthlink.net>,
	Tom Tromey <tromey@redhat.com>,
	 	Stan Shebs <stan@codesourcery.com>,
	Joel Brobecker <brobecker@adacore.com>,
	 	Michael Snyder <msnyder@vmware.com>
Cc: gdb-patches ml <gdb-patches@sourceware.org>
Subject: Re: [RFC] Let "gcore" command accept a suffix argument
Date: Wed, 06 Jan 2010 06:57:00 -0000	[thread overview]
Message-ID: <daef60381001052257q2068a8fbmaacd026b8d5cef49@mail.gmail.com> (raw)
In-Reply-To: <daef60381001040642h2e8b3919u221f61d43b23d395@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2210 bytes --]

Hello,

I make a new patch that eval command use "" to point out the simple command.
If want add " in normal string.  Use \"
If we want add \ in normal string.  Use \\
It can be use like:
(gdb) eval "echo \""$a++"\""
"7"(gdb) eval "echo \""$a++"\""
"8"(gdb) eval "echo \""$a++"\""
"9"(gdb) eval "echo \""$a++"\""
"10"(gdb) eval "echo \""$a++"\""
"11"(gdb) eval "echo \""$a++"\""
"12"(gdb) eval "echo \""$a++"\""
"13"(gdb) eval "echo \""$a++"\""

Please help me review it.

Best regards,
Hui

2010-01-06  Hui Zhu  <teawater@gmail.com>
	* printcmd.c (ctype.h): New include.
	(eval_command): New function.
	(_initialize_printcmd): New command "eval".



On Mon, Jan 4, 2010 at 22:42, Hui Zhu <teawater@gmail.com> wrote:
> Sorry for my poor English, did you mean that we can use "eval" for this command?
>
> Thanks,
> Hui
>
> On Thu, Dec 31, 2009 at 08:18, Stan Shebs <stanshebs@earthlink.net> wrote:
>> Tom Tromey wrote:
>>>>>>>>
>>>>>>>> "Stan" == Stan Shebs <stan@codesourcery.com> writes:
>>>>>>>>
>>>
>>> Stan> BTW, Pedro nudges me out of my stupor and reminds me that the
>>> Stan> soon-to-be-posted tracepoint action to evaluate without collecting
>>> is
>>> Stan> also called "eval" (it was originally proposed as "do" but that
>>> Stan> ambiguates with "down", which seemed like a bad idea).
>>>
>>> Stan> The two versions are not necessarily mutually exclusive - the
>>> Stan> downloading at the start of a trace run gives us a chance to filter
>>> Stan> out eval's that don't make sense for the target agent - but if we go
>>> Stan> too afield on syntax (the tracepoint version is simply a
>>> Stan> comma-separated list of GDB expressions), then that's going to be
>>> more
>>> Stan> of a problem to reconcile.
>>>
>>> "eval" seems awfully generic for a command which is specific to
>>> tracepoints.
>>>  I'm not super familiar with tracepoints but a lot of the other commands
>>> seem to start with "t".  Why not "teval"?
>>>
>>
>> That's a good idea.  If we ever come up with a Grand Unified Semantics of
>> actions and commands for which generic "eval" matches tracepoint "teval", we
>> can simply alias the two.
>>
>> Stan
>>
>>
>

[-- Attachment #2: eval.txt --]
[-- Type: text/plain, Size: 3156 bytes --]

---
 printcmd.c |  103 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 103 insertions(+)

--- a/printcmd.c
+++ b/printcmd.c
@@ -51,6 +51,8 @@
 #include "charset.h"
 #include "arch-utils.h"
 
+#include <ctype.h>
+
 #ifdef TUI
 #include "tui/tui.h"		/* For tui_active et.al.   */
 #endif
@@ -2649,6 +2651,104 @@ printf_command (char *arg, int from_tty)
   do_cleanups (old_cleanups);
 }
 
+static void
+eval_command (char *exp, int from_tty)
+{
+#define CMDSIZE 1024
+  char cmd[CMDSIZE + 1];
+  char *cmdp = cmd;
+  int is_eval = 1;
+  int is_backslash = 0;
+  int is_quote = 0;
+  char *eval_begin = exp;
+
+  if (!exp)
+    return;
+
+  while (cmdp - cmd < CMDSIZE)
+    {
+      if (!is_backslash && exp[0] == '\\')
+        {
+          is_backslash = 1;
+          exp ++;
+          continue;
+        }
+
+      if (is_eval)
+        {
+          if (!exp[0] || (exp[0]== '"' && !is_backslash))
+            {
+              struct value *value;
+              gdb_byte *buffer;
+              int length = -1;
+              struct type *char_type = NULL;
+              const char *la_encoding = NULL;
+              int is_end = 0;
+
+              if (!exp[0])
+                is_end = 1;
+              else
+                exp[0] = '\0';
+              if (strlen (eval_begin))
+                {
+                  value = parse_and_eval (eval_begin);
+
+                  switch (TYPE_CODE (value_type (value)))
+                    {
+                      case TYPE_CODE_ARRAY:
+                        LA_GET_STRING (value, &buffer, &length,
+                                       &char_type, &la_encoding);
+                       break;
+                      case TYPE_CODE_INT:
+                        buffer = plongest (value_as_long (value));
+                        length = strlen (buffer);
+                        break;
+                      default:
+                        buffer = eval_begin;
+                        length = exp - eval_begin;
+                        break;
+                    }
+
+                  if (length > CMDSIZE - (cmdp - cmd))
+                    length = CMDSIZE - (cmdp - cmd);
+                  memcpy (cmdp, buffer, length);
+                  cmdp += length;
+                }
+
+              if (is_end)
+                break;
+
+              is_eval = 0;
+            }
+
+          exp ++;
+        }
+      else
+        {
+          if (!exp[0])
+            break;
+
+          if (exp[0]== '"' && !is_backslash)
+            {
+              is_eval = 1;
+              eval_begin = exp + 1;
+            }
+          else
+            {
+              cmdp[0] = exp[0];
+              cmdp ++;
+            }
+          exp ++;
+        }
+
+      if (is_backslash)
+        is_backslash = 0;
+    }
+  cmdp[0] = '\0';
+
+  execute_command (cmd, from_tty);
+}
+
 void
 _initialize_printcmd (void)
 {
@@ -2812,4 +2912,7 @@ Show printing of source filename and lin
 			   NULL,
 			   show_print_symbol_filename,
 			   &setprintlist, &showprintlist);
+
+  add_com ("eval", no_class, eval_command, _("\
+Call command with variable."));
 }

  reply	other threads:[~2010-01-06  6:57 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4B11DA3C.3000203@vmware.com>
     [not found] ` <daef60380911300437o4c616eb2v5ad7bfe99bd3c5e9@mail.gmail.com>
     [not found]   ` <20091130162246.GE4034@adacore.com>
     [not found]     ` <4B141157.3070709@vmware.com>
     [not found]       ` <20091130185341.GI4034@adacore.com>
     [not found]         ` <4B141469.5030402@vmware.com>
     [not found]           ` <20091130190619.GJ4034@adacore.com>
     [not found]             ` <4B1428F0.7090608@vmware.com>
     [not found]               ` <daef60380912091827u6ff7127bp1d03998a40932914@mail.gmail.com>
2009-12-10  2:32                 ` Hui Zhu
2009-12-10 17:08                   ` Tom Tromey
2009-12-11 10:06                     ` Joel Brobecker
2009-12-11 18:25                       ` Tom Tromey
2009-12-12  8:33                         ` Hui Zhu
2009-12-13  4:05                           ` Hui Zhu
2009-12-14 17:09                           ` Tom Tromey
2009-12-15  1:57                             ` Hui Zhu
2009-12-15 19:21                               ` Tom Tromey
2009-12-16  3:58                                 ` Hui Zhu
2009-12-16 15:49                                   ` Stan Shebs
2009-12-17  2:45                                     ` Hui Zhu
2009-12-17  4:26                                       ` Joel Brobecker
2009-12-17  4:29                                         ` Michael Snyder
2009-12-17  9:32                                           ` Andreas Schwab
2009-12-21 20:15                                     ` Tom Tromey
2009-12-31  0:18                                       ` Stan Shebs
2010-01-04 14:42                                         ` Hui Zhu
2010-01-06  6:57                                           ` Hui Zhu [this message]
2010-01-06  7:58                                             ` Joel Brobecker
2010-01-09  9:55                                               ` Hui Zhu
2010-01-09 10:56                                                 ` Joel Brobecker
2010-01-09 15:18                                                   ` Hui Zhu
2010-01-10  5:43                                                     ` Joel Brobecker
2010-01-10 13:30                                                       ` Hui Zhu
2010-01-10 14:00                                                         ` Joel Brobecker
2010-01-10 14:16                                                           ` Hui Zhu
2010-06-21 15:05                                                           ` Hui Zhu
2010-06-21 16:57                                                             ` Joel Brobecker
2010-06-21 21:34                                                               ` Joel Brobecker
2010-06-21 21:40                                                             ` Tom Tromey
2010-06-22  7:29                                                               ` Hui Zhu
2010-06-22  9:50                                                                 ` Pedro Alves
2010-06-22 15:21                                                                 ` Joel Brobecker
2010-06-22 18:05                                                                 ` Eli Zaretskii
2010-06-23  2:03                                                                   ` Hui Zhu
2010-06-23 16:59                                                                     ` Joel Brobecker
2010-06-24  6:13                                                                       ` Hui Zhu
2010-01-06 10:13                                             ` Eli Zaretskii

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=daef60381001052257q2068a8fbmaacd026b8d5cef49@mail.gmail.com \
    --to=teawater@gmail.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=msnyder@vmware.com \
    --cc=stan@codesourcery.com \
    --cc=stanshebs@earthlink.net \
    --cc=tromey@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