From mboxrd@z Thu Jan 1 00:00:00 1970 Received: (from majordomo@localhost) by pauillac.inria.fr (8.7.6/8.7.3) id NAA03175; Sun, 27 Jan 2002 13:48:42 +0100 (MET) X-Authentication-Warning: pauillac.inria.fr: majordomo set sender to owner-caml-list@pauillac.inria.fr using -f Received: from concorde.inria.fr (concorde.inria.fr [192.93.2.39]) by pauillac.inria.fr (8.7.6/8.7.3) with ESMTP id NAA27946 for ; Sun, 27 Jan 2002 13:48:41 +0100 (MET) Received: from mail.cs.net.pl (cyber.cs.net.pl [62.233.142.98]) by concorde.inria.fr (8.11.1/8.11.1) with ESMTP id g0RCmef02448 for ; Sun, 27 Jan 2002 13:48:40 +0100 (MET) Received: by mail.cs.net.pl (Postfix, from userid 510) id 2E6CEAFB; Sun, 27 Jan 2002 13:48:37 +0100 (CET) Date: Sun, 27 Jan 2002 13:48:37 +0100 From: Tomasz Zielonka To: Gerd Stolpmann Cc: CAML list Subject: Re: [Caml-list] Problem with using oo in dynamically loaded bytecode ocaml runtime Message-ID: <20020127124837.GB22183@cs.net.pl> References: <20020127013519.GA20780@cs.net.pl> <20020127133648.A1247@ice.gerd-stolpmann.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020127133648.A1247@ice.gerd-stolpmann.de> User-Agent: Mutt/1.3.25i Sender: owner-caml-list@pauillac.inria.fr Precedence: bulk On Sun, Jan 27, 2002 at 01:36:48PM +0100, Gerd Stolpmann wrote: > On 2002.01.27 02:35 Tomasz Zielonka wrote: > > I did this kind of linking, too, but I did not have any problems. (I am > not loading into Postgresql, but into a Perl interpreter, but I think > this does not make any difference.) I have used -output-obj for a long > time, but recently (with the availability of O'Caml 3.04) I switched > to loading the bytecode directly. The debug sections are not lost, > and the Dynlink library works. [...] Thank you very much. I will try this method. > > When I make native/opt library _and_ define a method, I get corrupted > > memory in the postgresql backend. > > The generated code is not PIC, so it won't work. Yes. At some point it came to me and I was puzzled: why the hell it works (except for classes) when it shouldn't? > > So: > > 1) There is a bug, but where? In my program, in OCaml? > > It is more likely that the bug is in your program. Probably. But it happens inside caml_startup(), during initialization. > > 2) How to get stack backtrace in this situation? > > See my method. Stack backtraces work, even the debugger works if > you name the socket explicitly. Wow, that's cool. Will try. thank you, tom -- .-. Tomasz Zielonka CYBER SERVICE oo| programista http://www.cs.net.pl /`'\ zielony@cs.net.pl (\_;/) tel: [48] (22) 723-06-79 | tel/fax: [48] (22) 723-01-75 ------------------- Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/ To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr