From: Viet Le <vietlq85@gmail.com>
To: Alexey Egorov <alex.only.d@gmail.com>, caml-list@inria.fr
Subject: Re: [Caml-list] memory corruption using C stub
Date: Sat, 10 Jun 2017 15:40:41 +0000 [thread overview]
Message-ID: <CAG_8+G5Lk=m0rV_TbfPsCZUsL1+Y4A-c0jV0axGbGq1hSK58qw@mail.gmail.com> (raw)
In-Reply-To: <CAJannG4hB9jqpq8Hw=xkLACCUr0kAvF10A7X8iZX7eYhwDU0oQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1188 bytes --]
Do you have stack frame to look at?
On Sat, 10 Jun 2017 at 16:33, Alexey Egorov <alex.only.d@gmail.com> wrote:
> Hello,
>
> I have an OCaml application with some C code which (I believe) is the
> reason of some random crashes.
>
> Here is the code - https://pastebin.com/FVtLphZu
> This function reads file at given offset, divides data into chunks and
> compute checksums and compression ratio:
> external compute_data_props
> : string -> int -> int -> int -> (int * int * float) list =
> "compute_data_props"
>
> The problem is, after some calls to this stub, application is crashing
> at random places in OCaml code.
> I can't figure out what's going wrong, but replacing this stub with
> dummy function (which does nothing but returns some predefined list)
> eliminates the problem.
>
> What can we do to debug it? We are using OCaml 4.04.1 and Windows 10,
> and there is no other C stubs in our codebase.
>
> Thanks!
>
> --
> Caml-list mailing list. Subscription management and archives:
> https://sympa.inria.fr/sympa/arc/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>
--
Kind regards,
Viet
[-- Attachment #2: Type: text/html, Size: 2017 bytes --]
next prev parent reply other threads:[~2017-06-10 15:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-10 15:33 Alexey Egorov
2017-06-10 15:40 ` Viet Le [this message]
2017-06-10 17:00 ` Alexey Egorov
2017-06-10 15:44 ` Daniel Bünzli
2017-06-10 15:50 ` Daniel Bünzli
2017-06-10 16:01 ` Daniel Bünzli
2017-06-11 11:37 ` Alexey Egorov
2017-06-11 11:45 ` David Allsopp
2017-06-11 11:54 ` Alexey Egorov
2017-06-11 12:07 ` David Allsopp
2017-06-11 15:26 ` Alexey Egorov
2017-06-11 18:49 ` Alexey Egorov
2017-06-11 19:20 ` David Allsopp
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='CAG_8+G5Lk=m0rV_TbfPsCZUsL1+Y4A-c0jV0axGbGq1hSK58qw@mail.gmail.com' \
--to=vietlq85@gmail.com \
--cc=alex.only.d@gmail.com \
--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