Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Christopher Alexander Stein <stein@eecs.harvard.edu>
To: caml-list@inria.fr
Subject: Caml source line numbers in custom executable
Date: Mon, 10 Jan 2005 16:41:10 -0500 (EST)	[thread overview]
Message-ID: <20050110164053.L50586@bowser.eecs.harvard.edu> (raw)


Hi,

I am building a custom unstripped ELF executable that contains
the Caml runtime. The executable is segfaulting in runtime GC
routines. Can someone suggest how to cross reference these
routines with the corresponding file and line numbers of the Caml
source code so that gcc can tell me where the executable is
segfaulting?

Thank you

Lex

ps: Damien, I have tried using ocamldebug. It looks like an
excellent tool. In particular, it's time travel features are
powerful. However, in this case, it's use is limited by its
disconnected socket-based implementation; the executable
segfaults and the debugger loses contact.


             reply	other threads:[~2005-01-10 21:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-10 21:41 Christopher Alexander Stein [this message]
2005-01-12 16:57 ` [Caml-list] " 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=20050110164053.L50586@bowser.eecs.harvard.edu \
    --to=stein@eecs.harvard.edu \
    --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