public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Insight List <insight@sourceware.cygnus.com>
Subject: [Andrew Cagney <ac131313@cygnus.com>] Re: Patch: make `inferior_args' visible to gdbtk
Date: Thu, 07 Dec 2000 15:58:00 -0000	[thread overview]
Message-ID: <87wvdbai3e.fsf@creche.redhat.com> (raw)

Here's Andrew's response to my minor infcmd.c patch.

I can't do this work.  I guess this means that parts of session saving
will simply be useless for now.

Tom
------- Start of forwarded message -------
Message-ID: <3A301C99.A6C2D038@cygnus.com>
Date: Fri, 08 Dec 2000 10:26:17 +1100
From: Andrew Cagney <ac131313@cygnus.com>
MIME-Version: 1.0
To: tromey@redhat.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: Patch: make `inferior_args' visible to gdbtk
References: <87elzjdfa7.fsf@creche.redhat.com>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=us-ascii

Tom Tromey wrote:
> 
> I recently wrote a patch for Insight (aka gdbtk) to make it possible
> to save parts of the current session.  One thing that is saved is the
> inferior's arguments.  However, currently there is no good way for
> Insight to get this information from gdb.
> 
> Making the variable `inferior_args' non-static was the simplest way to
> accomplish this.
> 
> Ok?

No.  Insight needs to start using a formal interface into GDB.

	enjoy,
		Andrew



> 2000-11-28  Tom Tromey  <tromey@cygnus.com>
> 
>         * infcmd.c (inferior_args): No longer static.
> 
> Tom
> 
> Index: infcmd.c
> ===================================================================
> RCS file: /cvs/src/src/gdb/infcmd.c,v
> retrieving revision 1.13
> diff -u -r1.13 infcmd.c
> --- infcmd.c    2000/11/10 19:27:45     1.13
> +++ infcmd.c    2000/12/07 22:30:13
> @@ -118,7 +118,7 @@
>  /* String containing arguments to give to the program, separated by spaces.
>     Empty string (pointer to '\0') means no args.  */
> 
> -static char *inferior_args;
> +char *inferior_args;
> 
>  /* File name for default use for standard in/out in the inferior.  */
>

------- End of forwarded message -------

                 reply	other threads:[~2000-12-07 15:58 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=87wvdbai3e.fsf@creche.redhat.com \
    --to=tromey@redhat.com \
    --cc=insight@sourceware.cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).