From mboxrd@z Thu Jan 1 00:00:00 1970 Received: (from majordomo@localhost) by pauillac.inria.fr (8.7.6/8.7.3) id KAA24768; Thu, 23 Aug 2001 10:54:45 +0200 (MET DST) X-Authentication-Warning: pauillac.inria.fr: majordomo set sender to owner-caml-list@pauillac.inria.fr using -f Received: from concorde.inria.fr (concorde.inria.fr [192.93.2.39]) by pauillac.inria.fr (8.7.6/8.7.3) with ESMTP id KAA24331 for ; Thu, 23 Aug 2001 10:54:44 +0200 (MET DST) Received: from pauillac.inria.fr (pauillac.inria.fr [128.93.11.35]) by concorde.inria.fr (8.11.1/8.10.0) with ESMTP id f7N8seH17730; Thu, 23 Aug 2001 10:54:40 +0200 (MET DST) Received: (from xleroy@localhost) by pauillac.inria.fr (8.7.6/8.7.3) id KAA24630; Thu, 23 Aug 2001 10:54:39 +0200 (MET DST) Date: Thu, 23 Aug 2001 10:54:39 +0200 From: Xavier Leroy To: John Max Skaller Cc: David Mentre , caml-list@inria.fr Subject: Re: [Caml-list] Segfault in a native code program using pm variants Message-ID: <20010823105439.J22232@pauillac.inria.fr> References: <3B7C5A74.15141D95@maxtal.com.au> <3B7F0C99.FEDEAA86@maxtal.com.au> <3B82B493.BD6DCA52@maxtal.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <3B82B493.BD6DCA52@maxtal.com.au>; from skaller@maxtal.com.au on Wed, Aug 22, 2001 at 05:20:51AM +1000 Sender: owner-caml-list@pauillac.inria.fr Precedence: bulk John, David, and everyone else on this list, Please don't post this kind of message ("my OCaml program crashed, what's happening?") to caml-list. You're just annoying 500 subscribers who can't do anything about it. And even the Caml developers who are on the list can't do anything about it either as long as you don't provide a complete program that reproduces the crash. Here's how to proceed in this case: 0- Make sure that your program doesn't use unsafe features of OCaml: unchecked array and string accesses, Obj and Marshal functions, external C functions. If it does, look hard at those parts of your code and convince yourself that the bug is not there. 1- Package a program that reproduces the crash. It doesn't have to be small -- it's often hard to reduce a crash to a one-page fragment, and it's often not necessary. But make sure you include test inputs and commands that reproduce the crash. 2- Send a bug report to caml-bugs@inria.fr. If your package is large, better include a URL than attach it to your bug report, as our bug tracking system truncates large messages and doesn't handle attachments gracefully. Or, e-mail caml@inria.fr with your code attached. If you follow those three easy steps, you can rest assured that the Caml developers will investigate the issue quickly, and if it turns out to be a bug in OCaml, they'll fix it. If you don't, there is essentially nothing we can do to help you... Thanks for your attention, - Xavier Leroy ------------------- Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/ To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr