caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Xavier Leroy <Xavier.Leroy@inria.fr>
To: John Max Skaller <skaller@maxtal.com.au>
Cc: David Mentre <David.Mentre@inria.fr>, caml-list@inria.fr
Subject: Re: [Caml-list] Segfault in a native code program using pm variants
Date: Thu, 23 Aug 2001 10:54:39 +0200	[thread overview]
Message-ID: <20010823105439.J22232@pauillac.inria.fr> (raw)
In-Reply-To: <3B82B493.BD6DCA52@maxtal.com.au>; from skaller@maxtal.com.au on Wed, Aug 22, 2001 at 05:20:51AM +1000

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


      reply	other threads:[~2001-08-23  8:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-16  8:08 [Caml-list] Segfault in a native code multi-threaded program David Mentre
2001-08-16 12:45 ` Vitaly Lugovsky
2001-08-17  8:09   ` David Mentre
2001-08-17 16:54     ` Brian Rogoff
2001-08-20  9:12       ` David Mentre
2001-08-20 16:54       ` Jun P. FURUSE
2001-08-18 23:15     ` John Max Skaller
2001-08-19  0:24       ` John Gerard Malecki
2001-08-19 18:18         ` [Caml-list] Ocaml ffi release 1.2.2 dsfox
     [not found] ` <3B7C5A74.15141D95@maxtal.com.au>
     [not found]   ` <qtlitfm6ajh.fsf@pochi.inria.fr>
     [not found]     ` <3B7F0C99.FEDEAA86@maxtal.com.au>
     [not found]       ` <qtl3d6m4vkt.fsf@pochi.inria.fr>
2001-08-21 19:20         ` [Caml-list] Segfault in a native code program using pm variants John Max Skaller
2001-08-23  8:54           ` Xavier Leroy [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20010823105439.J22232@pauillac.inria.fr \
    --to=xavier.leroy@inria.fr \
    --cc=David.Mentre@inria.fr \
    --cc=caml-list@inria.fr \
    --cc=skaller@maxtal.com.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).