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: Command File Scope Checking


On 24/10/06, Eli Zaretskii <eliz@gnu.org> wrote:
> Date: Mon, 23 Oct 2006 22:08:19 +0100
> From: "Rob Quill" <rob.quill@gmail.com>
>
> But if I am stepping through the code, and a variable goes out of
> scope, how do you suggest I go about dealing with this?

Why do you need to ``deal'' with that?  I guess I don't understand
your problem, because I don't see any reason to care about such a
situation: at most, GDB will print an error message.

Can you show a small GDB script similar to what you use, and tell what
happens when a variable goes out of scope and how does that interfere
with the script?

I suppose you're right actually. Really I need to gert an implementation together and see how it goes before I worry about these problems. Thanks for your help, I'll keep yolu updated on how it goes.

Thanks,
Rob


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