caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Kenneth Adam Miller <kennethadammiller@gmail.com>
To: caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] Potential OCaml-ZMQ memory management problems
Date: Thu, 4 Dec 2014 16:48:09 -0500	[thread overview]
Message-ID: <CAK7rcp_w3xxwWxOKsAEOHrtqQSc-u50ZizXZSVcLSKM6=ZCL0g@mail.gmail.com> (raw)
In-Reply-To: <5480B7C3.90300@fugmann.net>

[-- Attachment #1: Type: text/plain, Size: 1474 bytes --]

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?


On Thu, Dec 4, 2014 at 2:36 PM, Anders Peter Fugmann <anders@fugmann.net>
wrote:

> Sending data over a zmq socket should not cause a segfault.
>
> I suggest that you open an issue on
> https://github.com/issuu/ocaml-zmq
> with exact details of the segfault and we can take a stab at it.
>
> /Anders
>
>
> On 04/12/14 17:45, Kenneth Adam Miller wrote:
>
>> Actually, I literally just found the location of the error... I'm trying
>> to send some data from ocaml that is causing ZMQ to segfault...
>>
>
>
>

[-- Attachment #2: Type: text/html, Size: 2418 bytes --]

  reply	other threads:[~2014-12-04 21:48 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 [this message]
2014-12-05  9:14                 ` Anders Fugmann
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='CAK7rcp_w3xxwWxOKsAEOHrtqQSc-u50ZizXZSVcLSKM6=ZCL0g@mail.gmail.com' \
    --to=kennethadammiller@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;
as well as URLs for NNTP newsgroup(s).