caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Jonathan Roewen <jonathan.roewen@gmail.com>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] The Bytecode Interpreter...
Date: Wed, 26 Oct 2005 23:20:56 +1300	[thread overview]
Message-ID: <ad8cfe7e0510260320h2555c415y650b71f6cea74b1@mail.gmail.com> (raw)
In-Reply-To: <ad8cfe7e0510260256x6651fc2l6d755a97acedda78@mail.gmail.com>

Hmm,

It might not be the interpreter afterall, or at least I'm ending up
with some very volatile machine code =/

Adding a printf() and a clear_screen() just before "res =
caml_interprete(caml_start_code, code_size);"
startup.c/caml_startup_code, and the problematic code runs fine...

So, not sure where the fault lies on this one... =/

On 10/26/05, Jonathan Roewen <jonathan.roewen@gmail.com> wrote:
> Hi once again,
>
> Hopefully this'll be my last problem to solve ;-)
>
> I've got ocamlrun + a bytecode app running on the bare metal, finally =)
>
> The following works fine:
>
> print_endline "Hello, World";;
>
> but, the following fails:
>
> Printf.printf "Hello, World\n%!";;
>
> with a print_endline statement before it, not even that gets run, so
> it appears to be a problem with loading the bytecode itself.
>
> The bytecode app is created using ocamlc -output-obj, and the .o file
> is linked into my kernel. I then call caml_startup(argv), where argv =
> { "" }.
>
> I've also experienced the same problem (appearing to not load/run the
> bytecode) when using Scanf & Hashtbl modules (so it's not isolated to
> Printf).
>
> What is the bytecode interpreter trying to do? Any clues? ;-) I'm
> trying to debug file open calls and things, but nothing appears to
> show up, and I don't get any errors printed to stdout/stderr by the
> interpreter.
>
> Jonathan
>


  reply	other threads:[~2005-10-26 10:20 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-21 10:01 Jonathan Roewen
2005-10-21 11:27 ` David MENTRE
2005-10-21 22:24   ` Jonathan Roewen
2005-10-21 23:49     ` Oliver Bandel
2005-10-22 21:33       ` Jonathan Roewen
2005-10-22  0:32     ` Jon Harrop
2005-10-22  0:39     ` Jacques Garrigue
2005-10-23  1:03   ` Jonathan Roewen
2005-10-23 10:21     ` Gerd Stolpmann
2005-10-24  5:38       ` Jonathan Roewen
2005-10-24  6:13         ` Jacques Garrigue
2005-10-24  6:48           ` Jonathan Roewen
2005-10-22  0:39 ` Jonathan Roewen
2005-10-26  0:33   ` Jonathan Roewen
2005-10-26  9:56 ` Jonathan Roewen
2005-10-26 10:20   ` Jonathan Roewen [this message]
2005-10-27 14:12   ` Damien Doligez
2005-10-28 21:41     ` Jonathan Roewen
2005-10-29 11:29       ` Gerd Stolpmann
2005-10-29 15:22         ` skaller
2005-10-30  0:41           ` Jonathan Roewen
2005-11-10 10:26         ` Damien Doligez

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=ad8cfe7e0510260320h2555c415y650b71f6cea74b1@mail.gmail.com \
    --to=jonathan.roewen@gmail.com \
    --cc=caml-list@yquem.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).