From: skaller <skaller@users.sourceforge.net>
To: Jon Harrop <jon@ffconsultancy.com>
Cc: caml-list <caml-list@yquem.inria.fr>
Subject: Re: [Caml-list] AMD64 segfault
Date: 14 May 2005 14:14:18 +1000 [thread overview]
Message-ID: <1116044057.17482.1010.camel@pelican.wigram> (raw)
In-Reply-To: <200505130233.27713.jon@ffconsultancy.com>
On Fri, 2005-05-13 at 11:33, Jon Harrop wrote:
> On Thursday 12 May 2005 23:35, skaller wrote:
[]
> Yes, the stack overflows much more quickly on AMD64 for me (pure64 Debian vs
> stock x86 Debian) and also causes a segfault instead of throwing
> Stack_overflow. I've no idea why.
Addresses are 64 bits instead of 32 .
> Try playing with ulimit to set the stack size and rerunning your program.
My ulimit is 8192, or 8Meg -- same as my 32 bit machine which
is a bit strange -- but it seems reasonable to me.
I tried 16M but it doesn't make any noticable difference.
I would suspect the stack size if the program processes smaller
files but failed on larger more complex ones, but that doesn't
seem to be the case. The fault now appears isolated to a single
function call, which suggests the Ocamlopt back end
code generator, particularly as introducing a diagnostic
sometimes fixes the problem (which would also cause a different
instruction sequence to be generated). OTOH a lot of functions
get called apparently without error before this point in the
program is reached, so perhaps not.
--
John Skaller, mailto:skaller@users.sf.net
voice: 061-2-9660-0850,
snail: PO BOX 401 Glebe NSW 2037 Australia
Checkout the Felix programming language http://felix.sf.net
next prev parent reply other threads:[~2005-05-14 4:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-12 22:35 skaller
2005-05-13 1:33 ` [Caml-list] " Jon Harrop
2005-05-14 4:14 ` skaller [this message]
2005-05-14 13:29 ` Jon Harrop
2005-05-13 8:14 ` skaller
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=1116044057.17482.1010.camel@pelican.wigram \
--to=skaller@users.sourceforge.net \
--cc=caml-list@yquem.inria.fr \
--cc=jon@ffconsultancy.com \
/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).