Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Julia Lawall <julia.lawall@lip6.fr>
To: caml-list@inria.fr
Subject: [Caml-list] segmentation fault
Date: Sun, 18 Jun 2017 21:41:45 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.20.1706182133490.30282@hadrien> (raw)

Hello,

I am trying to debug a segmentation fault in natively compiled ocaml code.
This blog says that the backtrace produced by gdb on a core file produced
by ocaml is not reliable:

https://incubaid.wordpress.com/2011/12/04/on-segmentation-faults-stack-overflows-gdb-and-ocaml/

Is that still the case?  The backtraces that I get look plausible, but
don't contain anything that looks like a stack overflow.  Over several
runs on two different laptops, the backtraces have nothing obvious in
common.  The bytecode version does not seem to stack overflow.  Adding
Gc.print_stat() at a periodic quiescent point in the execution did not
show a memory leak.  I am using OCaml 4.02.3.

thanks,
julia

             reply	other threads:[~2017-06-18 19:41 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-18 19:41 Julia Lawall [this message]
2017-06-19 20:15 ` David MENTRÉ
2017-06-19 20:58   ` Julia Lawall
2017-06-19 21:15     ` Josh Berdine
2017-06-19 21:19       ` Julia Lawall
2017-06-20  1:01         ` Francois BERENGER
2017-06-20  6:34           ` Julia Lawall
2017-06-21 14:20       ` Markus Weißmann
2017-06-23 17:03   ` SP
2017-06-23 17:25     ` Julia Lawall
2017-06-29 15:19       ` Damien Doligez
2017-06-29 15:26         ` Julia Lawall
2017-06-29 23:16         ` Julia Lawall
2017-06-30 10:55         ` Julia Lawall
2017-06-30 14:06           ` SP
2017-07-01 18:37         ` Julia Lawall
  -- strict thread matches above, loose matches on Subject: below --
2008-06-03  3:09 Segmentation fault Jacques Le Normand
2008-06-03 14:08 ` [Caml-list] " Berke Durak

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=alpine.DEB.2.20.1706182133490.30282@hadrien \
    --to=julia.lawall@lip6.fr \
    --cc=caml-list@inria.fr \
    /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