caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Jonathan Roewen <jonathan.roewen@gmail.com>
To: skaller <skaller@users.sourceforge.net>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] ocamlc -output-obj problems
Date: Tue, 15 Nov 2005 18:03:14 +1300	[thread overview]
Message-ID: <ad8cfe7e0511142103n5265af1jc026e62a4723a626@mail.gmail.com> (raw)
In-Reply-To: <1132028623.11813.99.camel@rosella>

> Maybe one of those is actually being used?
>
> Your basic argument is:
>
> (a) the make process works for normal Ocaml
> (b) you removed only unused functions from one library being linked in
>    by stubbing them out
> (c) now it crashes
>
> ==> contradiation.
>
> Clearly the most likely is that (b) is wrong :)

Perhaps, but I've tried adding a few, and can't find anything.

Anyways, how can I find out what the given bytecode instruction is?
I've added some debugging to caml_interprete() to list the how many
instructions have passed.

Here's an even simpler example of what causes my bytecode to 'crash':

external print_string: string -> unit = "my_print_string";;
let printf args = Printf.ksprintf print_string args;;
print_string "Kernel shutting down..";;

the declaration of printf above causes it to fail. comment it out, it's fine.

Jonathan


  reply	other threads:[~2005-11-15  5:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-15  3:52 Jonathan Roewen
2005-11-15  4:23 ` skaller
2005-11-15  5:03   ` Jonathan Roewen [this message]
     [not found]     ` <ad8cfe7e0511142131j4c53bae8td7f3af42e6cecf72@mail.gmail.com>
2005-11-15  5:32       ` Jonathan Roewen
2005-11-15  7:13         ` Jonathan Roewen
2005-11-15  8:14           ` Jonathan Roewen
2005-11-15 13:01             ` Alessandro Baretta
2005-11-15 13:33               ` skaller

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=ad8cfe7e0511142103n5265af1jc026e62a4723a626@mail.gmail.com \
    --to=jonathan.roewen@gmail.com \
    --cc=caml-list@yquem.inria.fr \
    --cc=skaller@users.sourceforge.net \
    /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).