From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from nez-perce.inria.fr (nez-perce.inria.fr [192.93.2.78]) by yquem.inria.fr (Postfix) with ESMTP id F2453BB91 for ; Fri, 10 Dec 2004 11:32:11 +0100 (CET) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.207]) by nez-perce.inria.fr (8.13.0/8.13.0) with ESMTP id iBAAWABX002373 for ; Fri, 10 Dec 2004 11:32:11 +0100 Received: by rproxy.gmail.com with SMTP id q1so610889rnf for ; Fri, 10 Dec 2004 02:32:10 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=r8HiW4/5epsEngTgz+OJGtZbEmeD6LJOu+SZQmhb8QnQ5xIG4rTkwpkLC/13+SmL0EZx2nVMvScggCBnwhckKbtLN+f4zmkX6FPEIpbKNxYBDbMI+lHZfE0fbiJ6M8/mzvVo6X76Bp/KFXBP2s/if0/g6Xp1U6gG/ms/DM5lT1g= Received: by 10.38.181.65 with SMTP id d65mr260329rnf; Fri, 10 Dec 2004 02:32:10 -0800 (PST) Received: by 10.38.65.29 with HTTP; Fri, 10 Dec 2004 02:32:10 -0800 (PST) Message-ID: <7f8e92aa041210023253d70662@mail.gmail.com> Date: Fri, 10 Dec 2004 12:32:10 +0200 From: Radu Grigore Reply-To: Radu Grigore To: caml-list@yquem.inria.fr Subject: Re: [Caml-list] Infinite loop when catching an exception In-Reply-To: <1102668710.2611.500.camel@pelican.wigram> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <41B91A9F.8050400@codefx.org> <16825.23709.530721.745815@gargle.gargle.HOWL> <1102668710.2611.500.camel@pelican.wigram> X-Miltered: at nez-perce with ID 41B97B2A.001 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)! X-Spam: no; 0.00; caml-list:01 sourceforge:01 wrote:01 bug:01 debugging:01 rubber:98 rubber:98 duck:98 exception:01 catching:02 chapter:02 dec:03 problem:05 problem:05 radu:05 X-Spam-Checker-Version: SpamAssassin 3.0.0 (2004-09-13) on yquem.inria.fr X-Spam-Status: No, score=0.0 required=5.0 tests=RCVD_BY_IP autolearn=disabled version=3.0.0 X-Spam-Level: On 10 Dec 2004 19:51:50 +1100, skaller wrote: > The best way to find this problem is post your code > to this list -- with experience you'll find the bug immediately > after pressing the Send button :) May be you just need to _pretend_ you are sending the question here :) (The Pragmatic Programmer has a chapter were it presents a "debugging technique" called "rubber ducking": talk to someone and explain the problem. That someone only needs to move his head as he's listening; it can even be a rubber duck, not a human) -- regards, radu http://rgrig.idilis.ro/