From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4633 invoked by alias); 6 May 2004 18:42:17 -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 4626 invoked from network); 6 May 2004 18:42:16 -0000 Received: from unknown (HELO omr1.netsolmail.com) (216.168.230.162) by sources.redhat.com with SMTP; 6 May 2004 18:42:16 -0000 Received: from ms5.netsolmail.com (IDENT:mirapoint@[216.168.230.178]) by omr1.netsolmail.com (8.12.10/8.12.10) with ESMTP id i46IgGdZ004766; Thu, 6 May 2004 14:42:16 -0400 (EDT) Received: from rivatek.dnsalias.net (rrcs-west-67-52-40-137.biz.rr.com [67.52.40.137]) by ms5.netsolmail.com (Mirapoint Messaging Server MOS 3.2.2-GA) with ESMTP id BGY00816; Thu, 6 May 2004 14:42:13 -0400 (EDT) Received: by rivatek.dnsalias.net (Postfix, from userid 500) id AE1E2A9DA2; Thu, 6 May 2004 13:42:12 -0500 (CDT) Date: Thu, 06 May 2004 18:42:00 -0000 From: Grant Edwards To: Ian Lance Taylor Cc: gdb@sources.redhat.com Subject: Re: How to tell gdb to exit? Message-ID: <20040506184211.GA13750@grante.dsl.visi.com> References: <20040506155013.GB12206@grante.dsl.visi.com> <20040506160943.GA12676@grante.dsl.visi.com> <20040506161646.GA12706@grante.dsl.visi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-SW-Source: 2004-05/txt/msg00053.txt.bz2 >> 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. One might think that the answer should occur while one is composing the message -- trying to explain the problem in sufficient detail for others to understand often sometimes reveals a solution. While this does happen, it also seems that at least as often the answer appears about 20 minutes later. > 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. I should try that... -- Grant Edwards grante@visi.com