Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Anders Fugmann <anders@fugmann.net>
To: Kenneth Adam Miller <kennethadammiller@gmail.com>,
	 caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] Potential OCaml-ZMQ memory management problems
Date: Fri, 05 Dec 2014 10:14:17 +0100	[thread overview]
Message-ID: <54817769.2050605@fugmann.net> (raw)
In-Reply-To: <CAK7rcp_w3xxwWxOKsAEOHrtqQSc-u50ZizXZSVcLSKM6=ZCL0g@mail.gmail.com>

On 12/04/2014 10:48 PM, Kenneth Adam Miller wrote:
> Well I am just no thorough and you are correct.
>
> The sending of data over a zmq socket and the conversion of that data
> from string to protobuf encoded string all occurred in one line. One I
> added a print statement and then segregated them more cleanly, I can see
> that it is most certainly the line that converts to protobuf.
>
> The exact function that fails (on my end, could be deeper within this)
> is to_pb from here:
>
> https://github.com/argp/bap/blob/master/ocaml/piqi/ast_piqi.ml#L186
>
> In any case, I did a test, and in my first function when to_pb gets
> called the first time and succeeds, I added an additional call to it...
> which also succeeded. But then in a subsequent unit test, the one that
> has been failing, still segfaults.
>
> If I turn off the tests prior to the segfaulting test, to_pb works in
> this particular run. But if the tests run before hand, something goes
> awry between the tests. Is it possible that to_pb is using some shared
> state between calls?

I would not expect so.

If you create a failing unittest that I could try?

Also, does the segfault contain a usable back trace (using gdb)? That 
might give some insights into which code is failing.

/Anders



  reply	other threads:[~2014-12-05  9:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-04  6:09 Kenneth Adam Miller
2014-12-04  7:55 ` Anders Fugmann
2014-12-04  8:02   ` Kenneth Adam Miller
2014-12-04  9:59     ` Anders Fugmann
2014-12-04 10:04       ` Kenneth Adam Miller
2014-12-04 16:39         ` Kenneth Adam Miller
2014-12-04 16:45           ` Kenneth Adam Miller
2014-12-04 19:36             ` Anders Peter Fugmann
2014-12-04 21:48               ` Kenneth Adam Miller
2014-12-05  9:14                 ` Anders Fugmann [this message]
2014-12-05 14:38                   ` Kenneth Adam Miller
2014-12-08 18:11                     ` Kenneth Adam Miller
2014-12-08 18:16                       ` Yotam Barnoy
2014-12-08 18:19                         ` Kenneth Adam Miller

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=54817769.2050605@fugmann.net \
    --to=anders@fugmann.net \
    --cc=caml-list@inria.fr \
    --cc=kennethadammiller@gmail.com \
    /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