From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-49672-listarch-gdb-patches=sources.redhat.com@sourceware.org>
Received: (qmail 31476 invoked by alias); 30 Jun 2007 18:22:09 -0000
Received: (qmail 31467 invoked by uid 22791); 30 Jun 2007 18:22:09 -0000
X-Spam-Check-By: sourceware.org
Received: from romy.inter.net.il (HELO romy.inter.net.il) (213.8.233.24)     by sourceware.org (qpsmtpd/0.31) with ESMTP; Sat, 30 Jun 2007 18:22:07 +0000
Received: from HOME-C4E4A596F7 (IGLD-84-228-245-109.inter.net.il [84.228.245.109]) 	by romy.inter.net.il (MOS 3.7.3-GA) 	with ESMTP id IFG05480 (AUTH halo1); 	Sat, 30 Jun 2007 21:22:00 +0300 (IDT)
Date: Sat, 30 Jun 2007 18:25:00 -0000
Message-Id: <uabuhmhfa.fsf@gnu.org>
From: Eli Zaretskii <eliz@gnu.org>
To: "Michael Snyder" <msnyder@sonic.net>
CC: drow@false.org, Michael.Snyder@access-company.com,         gdb-patches@sourceware.org
In-reply-to: <000b01c7bb2f$d88684e0$677ba8c0@sonic.net> (msnyder@sonic.net)
Subject: Re: [OB] Add cleanup, source.c
Reply-to: Eli Zaretskii <eliz@gnu.org>
References: <9270.12.7.175.2.1183069663.squirrel@webmail.sonic.net> <20070628224815.GC12578@caradoc.them.org> <655C3D4066B7954481633935A40BB36F041427@ussunex02.svl.access-company.com> <20070628231153.GA14231@caradoc.them.org> <11470.12.7.175.2.1183080998.squirrel@webmail.sonic.net> <20070629113407.GA13561@caradoc.them.org> <003201c7ba8c$d6e0e840$677ba8c0@sonic.net> <uejjtmz8z.fsf@gnu.org> <000b01c7bb2f$d88684e0$677ba8c0@sonic.net>
X-IsSubscribed: yes
Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-patches.sourceware.org>
List-Subscribe: <mailto:gdb-patches-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sourceware.org>
List-Help: <mailto:gdb-patches-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-patches-owner@sourceware.org
X-SW-Source: 2007-06/txt/msg00545.txt.bz2

> 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?