From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26760 invoked by alias); 21 Nov 2001 00:53:08 -0000 Mailing-List: contact insight-help@sourceware.cygnus.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: insight-owner@sources.redhat.com Received: (qmail 26678 invoked from network); 21 Nov 2001 00:53:05 -0000 X-Authentication-Warning: makita.cygnus.com: keiths owned process doing -bs Date: Thu, 04 Oct 2001 15:09:00 -0000 From: Keith Seitz To: Tom Tromey cc: Insight List Subject: Re: Startup with --args In-Reply-To: <87wv0lkmb9.fsf@creche.redhat.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2001-q4/txt/msg00047.txt.bz2 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 From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keith Seitz To: Tom Tromey Cc: Insight List Subject: Re: Startup with --args Date: Tue, 20 Nov 2001 16:53:00 -0000 Message-ID: References: <87wv0lkmb9.fsf@creche.redhat.com> X-SW-Source: 2001-q4/msg00348.html Message-ID: <20011120165300.qXEvkDTqWssKcY2YAvccoNxqBdl0Se89CxOwuk_qmzs@z> 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