0005074: wrong backtrace printed when mixing modules with and without debug info

View Issue Details [ Jump to Notes ]

[ Issue History ] [ Print ]

Project

Category

View Status

Date Submitted

Last Update

0005074

OCaml

OCaml general

public

2010-06-15 14:27

2012-09-18 13:38

Reporter

ygrek

Assigned To

Priority

high

Severity

minor

Reproducibility

always

Status

acknowledged

Resolution

open

Platform

OS Version

Product Version

3.11.2

Target Version

4.00.2+dev

Fixed in Version

Summary

0005074: wrong backtrace printed when mixing modules with and without debug info

Description

$ cat a.ml
exception Error
let fail () = raise Error

$ cat b.ml
let f () =
  ignore (A.fail ())

let () =
  (try failwith "oops" with _ -> ());
  f ()

$ cat run
ocamlc -c a.ml -o a.cmo
ocamlc -c -g b.ml -o b.cmo
ocamlc -g a.cmo b.cmo -o b.byte
ocamlopt -c a.ml -o a.cmx
ocamlopt -c -g b.ml -o b.cmx
ocamlopt -g a.cmx b.cmx -o b.native
OCAMLRUNPARAM=b ./b.byte
OCAMLRUNPARAM=b ./b.native

$ ./run
Fatal error: exception A.Error
Called from file "b.ml", line 2, characters 9-20
Called from file "b.ml", line 6, characters 2-6
Fatal error: exception A.Error
Raised at file "pervasives.ml", line 22, characters 22-33
Called from file "b.ml", line 5, characters 7-22

The backtrace for b.native is absolutely wrong.
Note that a.ml is compiled without -g option.

Additional Information

Funny thing - if module A raises predefined exception instead of newly defined Error - everything is ok.
Minor note - no "Raised at" printed for b.byte

Tags

No tags attached.

Attached Files

Relationships

Notes
There are no notes attached to this issue.

Issue History
Date Modified	Username	Field	Change
2010-06-15 14:27	ygrek	New Issue
2011-06-01 23:14	doligez	Status	new => acknowledged
2012-07-10 20:17	doligez	Target Version	=> 4.01.0+dev
2012-07-31 13:36	doligez	Target Version	4.01.0+dev => 4.00.1+dev
2012-09-18 13:38	doligez	Priority	normal => high
2012-09-18 13:38	doligez	Target Version	4.00.1+dev => 4.00.2+dev