From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@sympa.inria.fr Delivered-To: caml-list@sympa.inria.fr Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by sympa.inria.fr (Postfix) with ESMTPS id D246E7FB13 for ; Thu, 4 Dec 2014 20:36:38 +0100 (CET) Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of anders@fugmann.net) identity=pra; client-ip=90.184.182.235; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="anders@fugmann.net"; x-sender="anders@fugmann.net"; x-conformance=sidf_compatible Received-SPF: Pass (mail2-smtp-roc.national.inria.fr: domain of anders@fugmann.net designates 90.184.182.235 as permitted sender) identity=mailfrom; client-ip=90.184.182.235; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="anders@fugmann.net"; x-sender="anders@fugmann.net"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of postmaster@fw.fugmann.net) identity=helo; client-ip=90.184.182.235; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="anders@fugmann.net"; x-sender="postmaster@fw.fugmann.net"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AuYAADG3gFRauLbrfGdsb2JhbABZgmR0g13DTIYQCgKBNQEBAQEBEQEBCxYFRIQDAQEEIxVRCxgCAgUhAgIPAkYGAQwIAog7AwnAOpZvAQEIAQEBAQEZBIErjASDPoJxgVEBBJQmnkaDMwEBAQ X-IPAS-Result: AuYAADG3gFRauLbrfGdsb2JhbABZgmR0g13DTIYQCgKBNQEBAQEBEQEBCxYFRIQDAQEEIxVRCxgCAgUhAgIPAkYGAQwIAog7AwnAOpZvAQEIAQEBAQEZBIErjASDPoJxgVEBBJQmnkaDMwEBAQ X-IronPort-AV: E=Sophos;i="5.07,517,1413237600"; d="scan'208";a="111134788" Received: from 0405ds1-vaer.1.fullrate.dk (HELO fw.fugmann.net) ([90.184.182.235]) by mail2-smtp-roc.national.inria.fr with ESMTP/TLS/ADH-AES256-SHA; 04 Dec 2014 20:36:38 +0100 Received: from [IPv6:2001:470:dc46:1:daa2:5eff:fe95:453e] (zaphod.fugmann.net [IPv6:2001:470:dc46:1:daa2:5eff:fe95:453e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fw.fugmann.net (Postfix) with ESMTPSA id F25EE169CA1F; Thu, 4 Dec 2014 20:36:35 +0100 (CET) Message-ID: <5480B7C3.90300@fugmann.net> Date: Thu, 04 Dec 2014 20:36:35 +0100 From: Anders Peter Fugmann User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.2.0 MIME-Version: 1.0 To: Kenneth Adam Miller , caml users References: <54801373.3010506@fugmann.net> <5480309B.3020402@fugmann.net> In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Validation-by: anders@fugmann.net Subject: Re: [Caml-list] Potential OCaml-ZMQ memory management problems 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...