From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1233 invoked by alias); 6 May 2004 18:36:33 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 1226 invoked from network); 6 May 2004 18:36:32 -0000 Received: from unknown (HELO yosemite.airs.com) (209.128.65.135) by sources.redhat.com with SMTP; 6 May 2004 18:36:32 -0000 Received: (qmail 16700 invoked by uid 10); 6 May 2004 18:36:31 -0000 Received: (qmail 13625 invoked by uid 500); 6 May 2004 18:36:18 -0000 From: Ian Lance Taylor To: Grant Edwards Cc: gdb@sources.redhat.com Subject: Re: How to tell gdb to exit? References: <20040506155013.GB12206@grante.dsl.visi.com> <20040506160943.GA12676@grante.dsl.visi.com> <20040506161646.GA12706@grante.dsl.visi.com> Date: Thu, 06 May 2004 18:36:00 -0000 In-Reply-To: <20040506161646.GA12706@grante.dsl.visi.com> Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2004-05/txt/msg00052.txt.bz2 Grant Edwards writes: > I messed around with this on and off for days, and couldn't > find the answer, but as soon as I put my foot in my mouth > publically, the answer appears. Odd, that. I actually find that this is a fairly effective technique for solving a problem. Send out a message, and then the answer occurs to you. The more people to whom you send the message, the more likely you are to find the answer yourself. I've learned to exploit this fact by composing the message but delaying the actual sending for a period of time. Sometimes the answer will come to me before the message actually goes out. You may think I'm kidding, but I'm not. At least not wholly. Ian