From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@yquem.inria.fr Delivered-To: caml-list@yquem.inria.fr Received: from mail4-relais-sop.national.inria.fr (mail4-relais-sop.national.inria.fr [192.134.164.105]) by yquem.inria.fr (Postfix) with ESMTP id 0F99CBBAF for ; Mon, 8 Nov 2010 15:48:22 +0100 (CET) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AtoAAPeb10zRVdY0k2dsb2JhbACDMJAljioIFQEBAQEJCQoJEQMfoyCJI4JThSOJBwEBAwWBHYMzcwSEWIV9iSQ X-IronPort-AV: E=Sophos;i="4.58,314,1286143200"; d="scan'208";a="77461405" Received: from mail-bw0-f52.google.com ([209.85.214.52]) by mail4-smtp-sop.national.inria.fr with ESMTP; 08 Nov 2010 15:48:21 +0100 Received: by bwz6 with SMTP id 6so4704143bwz.39 for ; Mon, 08 Nov 2010 06:48:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type; bh=tn9On+8Xp07nnF8DBpb0peltVnL908rMOG1MHe9KW3A=; b=SsJKGkRmwt8Do/CCstNRW6n8RtH2FF3IrIP/n5yrtqTwfAXdtN6/5Kc8RWa5B+Xvyt XrAUxueVAC/2149wvUupQDR/caw5PQml5JOusJQom2eYKyUeAumN/po6o6+pq7mj8NsH 1qzC0sAkM1nFJFF5kSf7lg5Aa72u+GDVaKNEc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=i2Ip0VpiDAKipiNeIe9beBePnMZlU+XAWuJfCtVOB10bSr7fEeEm1O5cBZAmW/GVKO M0pOhuPvjUH5RrQnZODUMHlLElqjKeAMclV/TERh2VHB+zwMwGq4Ch/AC2e83QcLw99R oUGr2EU7L0oM+RquylswjNnF9rTJKwFkk3jfk= MIME-Version: 1.0 Received: by 10.204.114.77 with SMTP id d13mr4953920bkq.150.1289227701210; Mon, 08 Nov 2010 06:48:21 -0800 (PST) Sender: till.varoquaux@gmail.com Received: by 10.204.50.200 with HTTP; Mon, 8 Nov 2010 06:48:21 -0800 (PST) In-Reply-To: References: <384325291.294734.1288998871132.JavaMail.root@zmbs3.inria.fr> <20101106025118.GA23041@yquem.inria.fr> Date: Mon, 8 Nov 2010 09:48:21 -0500 X-Google-Sender-Auth: 26HoOnFFdCqUyz8XLu7PtKtXdG0 Message-ID: Subject: Re: [Caml-list] Causes for segfaults From: Till Varoquaux To: Jamie Brandon Cc: caml-list@yquem.inria.fr Content-Type: text/plain; charset=UTF-8 X-Spam: no; 0.00; segfaults:01 backtrace:01 cheers:01 bytecode:01 marshalling:01 marshalling:01 ulimit:01 beginner's:01 ocaml:01 bug:01 brandon:98 beginners:01 wrote:01 stack:01 stack:01 That's an odd backtrace. As far as I can tell you have compiled everything fine yet it tells me that run_query is blowing up in a subcall to caml_ml_close_channel (which is the underlying c call for close_in and close_out). I might be reading this bt wrong. Otherwise there's something fishy with your stack. Whatever it is, I am very confused by this all. Would you mind posting your code to see if other people can reproduce the problem? Cheers, Till On Mon, Nov 8, 2010 at 9:26 AM, Jamie Brandon wrote: >> If it is, perhaps try to limit it and try again in bytecode to see >> if the Segmentation Fault is transformed into a Stack Overflow. > > Marshalling is not tail-recursive, so I will always get a stack > overflow marshalling this much data. Setting ulimit -s unlimited > prevents this but also obscures the current problem. > > _______________________________________________ > Caml-list mailing list. Subscription management: > http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list > Archives: http://caml.inria.fr > Beginner's list: http://groups.yahoo.com/group/ocaml_beginners > Bug reports: http://caml.inria.fr/bin/caml-bugs >