Version française
Home     About     Download     Resources     Contact us    

This site is updated infrequently. For up-to-date information, please visit the new OCaml website at

Browse thread
[Caml-list] Problem with using oo in dynamically loaded bytecode ocaml runtime
[ Home ] [ Index: by date | by threads ]
[ Search: ]

[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
Date: 2002-01-27 (12:48)
From: Tomasz Zielonka <zielony@c...>
Subject: Re: [Caml-list] Problem with using oo in dynamically loaded bytecode ocaml runtime
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.


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,

   .-.   Tomasz Zielonka                           CYBER SERVICE
   oo|   programista              
 (\_;/)  tel: [48] (22) 723-06-79 | tel/fax: [48] (22) 723-01-75
Bug reports:  FAQ:
To unsubscribe, mail  Archives: