This is the mail archive of the gdb-patches@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: [OB] Add cleanup, source.c

> From: "Michael Snyder" <msnyder@sonic.net>
> Cc: <drow@false.org>, <Michael.Snyder@access-company.com>,
>         <gdb-patches@sourceware.org>
> Date: Sat, 30 Jun 2007 09:00:56 -0700
> 
> Depends on what the "cleanups" are, I suppose.  Those I'm familiar
> with are mostly xfrees, fcloses, etc.  Doesn't really matter what
> order they are performed in, so long as they get done before the
> next command loop cycle.

Yes, but discard_cleanups throws them away without performing them.  I
don't believe you won't care about that.

> Can you give me an example of such non-deterministic behavior?

What for?  Isn't it obvious, that, given the user-driven workings of
GDB, you can never know when will the next discard_cleanups call
happen?
Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]