caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Ashish Agarwal <agarwal1975@gmail.com>
To: Caml List <caml-list@inria.fr>
Subject: [Caml-list] printing an exception changes printed backtrace
Date: Fri, 14 Jan 2011 16:15:15 -0500	[thread overview]
Message-ID: <AANLkTikznXV-ORo1P=ar49kAYnq7_nKygJvS--z4r7kY@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1064 bytes --]

I observe the following unexpected behavior:

--- a.ml ---
try
  … some code ...
with e ->
(*  Printf.eprintf "%s\n" (Printexc.to_string e); *)
  Printexc.print_backtrace Legacy.stderr
------

Compiling as ocamlopt -g a.ml gives:
$ ./a.out
Raised at file "fool.ml", line 162, characters 13-22
Called from file "bar.ml", line 13, characters 5-56
Called from file "bar.ml", line 43, characters 4-63

Now this doesn't say which exception was raised, so I uncomment the
commented line. I'm expecting the identical output, but with the exception
printed first. However, I get:

$ ./a.out
Not_found
Raised at file "hashtbl.ml", line 93, characters 19-28

So it appears that printing an exception changes the backtrace. Is that
possible?

Unfortunately, I cannot reproduce this behavior in a minimal example. The
following script behaves as expected:

--- b.ml ---
let f () = raise (Failure "")
let g () = f ()
let _ =
  try g()
  with e ->
    (* Printf.eprintf "%s\n" (Printexc.to_string e); *)
    Printexc.print_backtrace stderr

[-- Attachment #2: Type: text/html, Size: 1736 bytes --]

             reply	other threads:[~2011-01-14 21:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-14 21:15 Ashish Agarwal [this message]
2011-01-14 21:59 ` Daniel Bünzli
2011-01-14 22:05   ` Ashish Agarwal
2011-01-17 15:37 ` xclerc
2011-01-17 16:41   ` Ashish Agarwal
2011-01-17 17:02     ` Xavier Clerc
2011-01-17 17:12       ` Ashish Agarwal

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='AANLkTikznXV-ORo1P=ar49kAYnq7_nKygJvS--z4r7kY@mail.gmail.com' \
    --to=agarwal1975@gmail.com \
    --cc=caml-list@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).