caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Kenneth Knowles <kknowles@berkeley.edu>
To: Thomas Fischbacher <Thomas.Fischbacher@Physik.Uni-Muenchen.DE>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] segfault in Unix.gethostbyname
Date: Fri, 26 Mar 2004 11:24:38 -0800	[thread overview]
Message-ID: <20040326192438.GA18128@tallman.kefka.frap.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0403261929070.26695@seekar.cip.physik.uni-muenchen.de>


> Hm. Have you had a look at ltrace output?

I have now, but I'm not really familiar with ltrace, and I'm not sure how to
interpret it...

kenn@tallman gethost $ ltrace -l /lib/libnss_wins.so.2 ocamlrun ocaml unix.cma
        Objective Caml version 3.07+2

# Unix.gethostbyname "dbdev";;
--- SIGSEGV (Segmentation fault) ---
+++ killed by SIGSEGV +++

There is no output, but isn't that contradictory with where gdb finds the
segfault?

Without the -l option, the last few lines look like this (there's way too much
memmove stuff to paste):

  free(0x809ba38)                                                  = <void>
  free(0x80a14a0)                                                  = <void>
  malloc(28)                                                       = 0x8092698
  memmove(0x08092698, 0x401dcfe0, 28, 0x08059747, 28)              = 0x08092698
  malloc(6)                                                        = 0x80926b8
--- SIGSEGV (Segmentation fault) ---
+++ killed by SIGSEGV +++


I'm not sure what this signifies.

Kenn

-------------------
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


  reply	other threads:[~2004-03-26 19:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-26 18:22 Kenneth Knowles
2004-03-26 18:30 ` Thomas Fischbacher
2004-03-26 19:24   ` Kenneth Knowles [this message]
2004-03-26 19:00 ` Blair Zajac
2004-03-26 19:27   ` Kenneth Knowles

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=20040326192438.GA18128@tallman.kefka.frap.net \
    --to=kknowles@berkeley.edu \
    --cc=Thomas.Fischbacher@Physik.Uni-Muenchen.DE \
    --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).