Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Richard Sharpe <rsharpe@richardsharpe.com>
To: <gdb@sources.redhat.com>
Subject: Processing of convenience variables for scripts ...
Date: Fri, 06 Dec 2002 08:30:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.33.0212060853160.30583-100000@ns.aus.com> (raw)

Hi,

In looking at this issue, it seems that much of the existing code that 
deals with variables is centered around printing:

   value_print (var->value, gdb_stdout, 0, Val_pretty_default);

While it seems that I could mess with providing new functions for a stream 
structure that I could retrieve strings from, is there a simpler way.

I envision something like 

  var1 = value_to_string (var->value);

And then construct a new command, and pass it through the standard routine 
that processes commands. 

However, it seems that things are not that simple :-)

Regards
-----
Richard Sharpe, rsharpe[at]ns.aus.com, rsharpe[at]samba.org, 
sharpe[at]ethereal.com, http://www.richardsharpe.com


             reply	other threads:[~2002-12-06 16:30 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-06  8:30 Richard Sharpe [this message]
2002-12-06  8:41 ` Daniel Jacobowitz
2002-12-06  8:54   ` Fernando Nasser
2002-12-06 11:57     ` Richard Sharpe
2002-12-06 14:53       ` Fernando Nasser
2002-12-06 17:17         ` Daniel Jacobowitz
2002-12-07  8:50   ` Richard Sharpe
  -- strict thread matches above, loose matches on Subject: below --
2002-11-20  0:48 Richard Sharpe
2002-11-20  6:13 ` Daniel Jacobowitz
2002-11-20  8:32   ` Andrew Cagney
2002-11-20  8:36     ` Daniel Jacobowitz
2002-11-20  9:28       ` Richard Sharpe
2002-11-20 10:36         ` Daniel Jacobowitz
2002-11-20 21:40           ` Eli Zaretskii
2002-12-05 16:52           ` Fernando Nasser
2002-12-08 11:36           ` Doug Evans
2002-12-08 12:30             ` Daniel Jacobowitz
2002-12-08 12:52               ` Doug Evans
2002-12-08 11:16   ` Doug Evans
2002-12-08 11:31     ` Richard Sharpe

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=Pine.LNX.4.33.0212060853160.30583-100000@ns.aus.com \
    --to=rsharpe@richardsharpe.com \
    --cc=gdb@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