This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Step command in command file

From: "Rob Quill" <rob dot quill at gmail dot com>
To: "Jim Blandy" <jimb at codesourcery dot com>
Cc: gdb at sourceware dot org
Date: Tue, 28 Nov 2006 11:33:21 +0000
Subject: Re: Step command in command file
References: <baf6008d0611230538x5374f1f4x6ca8fa36b08205d@mail.gmail.com> <m3hcwku0b5.fsf@codesourcery.com>

On 27/11/06, Jim Blandy <jimb@codesourcery.com> wrote:


"Rob Quill" <rob.quill@gmail.com> writes:
> When I use the step command in a command file it makes one step, but
> then stops executing the script. Is there a way to stop this form
> happening? It does not happen with next or nexti.

Can you give us more details?  An example program and script, and a
transcript of a GDB session misbehaving?


My mistake, it is to do with the less than ideal way that I have
checked to see if a variable is in scope.

Rob

References:
- Step command in command file
  - From: Rob Quill
- Re: Step command in command file
  - From: Jim Blandy

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]