public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Keith Seitz <keiths@cygnus.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Insight List <insight@sourceware.cygnus.com>
Subject: Re: Startup with --args
Date: Tue, 20 Nov 2001 16:53:00 -0000	[thread overview]
Message-ID: <Pine.GSO.4.33.0111201649230.20281-100000@makita.cygnus.com> (raw)
Message-ID: <20011120165300.qXEvkDTqWssKcY2YAvccoNxqBdl0Se89CxOwuk_qmzs@z> (raw)
In-Reply-To: <87wv0lkmb9.fsf@creche.redhat.com>

On 20 Nov 2001, Tom Tromey wrote:

> I've been running with my --args patch installed for a while now.
> Hopefully it will get its final approval soon.

Are you waiting on me for something?

> I'd like to check in this patch after my --args patch goes in.
> Ok?

Is there a way to do this without modifying session_notice_file_change? I
don't know. It seems to me that if we want to override the session's
arguments, we should just do that.

> -    # must notice the initial session by hand.
> -    session_notice_file_change
> +    # must notice the initial session by hand.  We pass in the
> +    # arguments, if they exist -- if the user used `gdb --args' then
> +    # we want the new arguments to override the session's arguments.
> +    session_notice_file_change [gdb_get_inferior_args]

Soemthing like:

   set gdb_args [gdb_get_inferior_args]
   session_notice_file_change
   gdb_set_inferior_args $gdb_args

I don't know. It just semes like an odd thing to put in
session_notice_file_change, but maybe my brain is away right now.

?
Keith


  reply	other threads:[~2001-11-20 16:53 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-04 14:36 Tom Tromey
2001-10-04 15:09 ` Keith Seitz [this message]
2001-10-04 18:08   ` Tom Tromey
2001-10-04 18:44     ` Keith Seitz
2001-10-04 19:13       ` Tom Tromey
2001-11-21 16:26         ` Tom Tromey
2001-11-21 14:45       ` Keith Seitz
2001-11-21 14:38     ` Tom Tromey
2001-11-20 16:53   ` Keith Seitz
2001-11-20 16:19 ` Tom Tromey
2001-10-04 19:28 Keith Seitz
2001-11-21 23:13 ` Keith Seitz
2001-10-04 19:35 Tom Tromey
2001-11-21 23:14 ` Tom Tromey
2001-10-04 19:42 Tom Tromey
2001-11-21 23:18 ` Tom Tromey

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.GSO.4.33.0111201649230.20281-100000@makita.cygnus.com \
    --to=keiths@cygnus.com \
    --cc=insight@sourceware.cygnus.com \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).