<?xml version="1.0" encoding="ISO-8859-1"?>

<!DOCTYPE message PUBLIC
  "-//MLarc//DTD MLarc output files//EN"
  "../../mlarc.dtd"[
  <!ATTLIST message
    listname CDATA #REQUIRED
    title CDATA #REQUIRED
  >
]>

  <?xml-stylesheet href="../../mlarc.xsl" type="text/xsl"?>


<message 
  url="2003/12/58db6af4f59fb2639367ca79e4b81602"
  from="Yaron M. Minsky &lt;yminsky@c...&gt;"
  author="Yaron M. Minsky"
  date="2003-12-02T20:50:44"
  subject="[Caml-list] getting stack traces in running code"
  prev="2003/12/95e09e33572c3bc85a9fa3c1550cb20e"
  next="2003/12/8d160e1869335ab568e3f6d10a7c6300"
  next-in-thread="2003/12/8d160e1869335ab568e3f6d10a7c6300"
  prev-thread="2003/12/aa9745fef14bf44399b3477e558c0113"
  next-thread="2003/12/c77a2d55b7855bb7129ecef3d8503541"
  root="../../"
  period="month"
  listname="caml-list"
  title="Archives of the Caml mailing list">

<thread subject="[Caml-list] getting stack traces in running code">
<msg 
  url="2003/12/58db6af4f59fb2639367ca79e4b81602"
  from="Yaron M. Minsky &lt;yminsky@c...&gt;"
  author="Yaron M. Minsky"
  date="2003-12-02T20:50:44"
  subject="[Caml-list] getting stack traces in running code">
<msg 
  url="2003/12/8d160e1869335ab568e3f6d10a7c6300"
  from="Richard Jones &lt;rich@a...&gt;"
  author="Richard Jones"
  date="2003-12-02T21:45:36"
  subject="Re: [Caml-list] getting stack traces in running code">
</msg>
<msg 
  url="2003/12/1d631fdc6491f61c7bc538f7bbf45d0d"
  from="Issac Trotts &lt;ijtrotts@n...&gt;"
  author="Issac Trotts"
  date="2003-12-02T22:25:32"
  subject="Re: [Caml-list] getting stack traces in running code">
<msg 
  url="2003/12/03846a1812e0e09a7bd0b8f6f6ed02d6"
  from="Nicolas Cannasse &lt;warplayer@f...&gt;"
  author="Nicolas Cannasse"
  date="2003-12-03T03:25:26"
  subject="Re: [Caml-list] getting stack traces in running code">
<msg 
  url="2003/12/bd06ee9099e75c3d3e1ca4d8b3a79021"
  from="Damien Doligez &lt;damien.doligez@i...&gt;"
  author="Damien Doligez"
  date="2003-12-03T14:19:17"
  subject="Re: [Caml-list] getting stack traces in running code">
</msg>
<msg 
  url="2003/12/36cd132d9e5998a8717e6be5bbc8a40c"
  from="Issac Trotts &lt;ijtrotts@c...&gt;"
  author="Issac Trotts"
  date="2003-12-04T22:22:03"
  subject="Re: [Caml-list] getting stack traces in running code">
</msg>
</msg>
</msg>
</msg>
</thread>

<contents>
Is there a reason why stack traces are available only on a crash?  I
have a project (a distributed OpenPGP keyserver system,
http://www.nongnu.org/sks/) that is a long-running daemon.  Unexpected
errors are caught and logged, but unfortunately, there's no way of
getting a stack-trace, since I don't let the exceptions kill the
program.  This makes debugging much more difficult, and is one of the
single largest difficulties I have with ocaml.  Is there a technical
reason that a bytecode-compiled executable couldn't have access to the
stack trace during execution?

y

-- 
|--------/            Yaron M. Minsky              \--------|
|--------\ http://www.cs.cornell.edu/home/yminsky/ /--------|

Open PGP --- KeyID B1FFD916
Fingerprint: 5BF6 83E1 0CE3 1043 95D8 F8D5 9F12 B3A9 B1FF D916


-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners

</contents>

</message>

