Poly/ML

polyml@lists.polyml.org

698 discussions

Segfault on 2.6.9 SMP
by Martin.vGagern＠gmx.net 13 Dec '04

13 Dec '04

Hello! I know this problem was already mentioned in two threads. Still I have additional information. Addition to "Segfault on SMP Linux kernels": I get those problems on the /third/ call to ReserveAddressSpace: (compiled with -O0, otherwise ReserveAddressSpace will be inlined) #0 ReserveAddressSpace (addr=0x3f000000 <Address 0x3f000000 out of bounds>, len=8192) at mmap.c:364 #1 0x080591fe in ReserveMLSpace ( bottom=0x3f000000 <Address 0x3f000000 out of bounds>, top=0x3f002000 <Address 0x3f002000 out of bounds>) at mmap.c:378 #2 0x080592f1 in ReserveMLSpaces () at mmap.c:406 #3 0x080521f3 in main (argc=1, argv=0xbfffe4f4) at mpoly.c:710 Addition to "Seg. fault - 2.6.9 kernel": I have a plain vanilla 2.6.9, no patches. Still this does not work for me. I have a gentoo distribution, maybe you want to keep an eye on the related gentoo bug report as well: http://bugs.gentoo.org/show_bug.cgi?id=35548 I only had a rather brief look at the source code, but is there a special reason why the mmapped area should be at a fixed address? Greetings, Martin von Gagern

2 2

Segfault on SMP Linux kernels
by plam＠MIT.EDU 01 Dec '04

01 Dec '04

Hi all, I was trying to run polyml on a machine running a 2.6.9-smp kernel. Unfortuantely, it just segfaults when it tries to mmap, in particular at the second call to ReserveAddressSpace in mmap.c: caddr_t pa = mmap((caddr_t)addr, len, PROT_NONE, MAP_PRIVATE | MAP_FIXED | MAP_NORESERVE | MAP_ANONYMOUS, -1, 0L); System details: 1G of RAM, Debian unstable, libc6 2.3.2.ds1-18, kernel 2.6.9-smp. It does not crash when I use the 2.6.8 non-smp kernel. Thanks for any help. pat

1 0

Turning off printing of exceptions
by rda＠lemma-one.com 04 Nov '04

04 Nov '04

I have a recollection that there is a way of stopping Poly/ML printing out the exception value when an excepation is raised but not caught, but I can't find anything in the structure PolyML that looks likely to do this. Am I mistaken or am I overlooking something? Regards, Rob.

3 4

'not a trap instruction' crash in Mac OS X 10.3
by David.Matthews＠prolingua.co.uk 04 Nov '04

04 Nov '04

Larry Paulson has been having a crash with Poly/ML on Mac OS X. It fails with a message of the form: MD_trap_handler1: 0x81840000 is not a trap instruction; pc = 0x1f208 The details vary but in each case the hex value after MD_trap_handler1 (the actual trapping instruction) begins 0x8 indicating a LOAD instruction. I haven't been able to reproduce the problem but that may be because I'm using OS X 10.2 . Has anyone else had crashes of this sort on Mac OS X? David.

1 0

Development release
by David.Matthews＠prolingua.co.uk 02 Nov '04

02 Nov '04

I've now put the development sources on to the Poly/ML website as http://www.polyml.org/polyml-devel.tar.gz . All the patches I've received should be included but I'd be grateful if people could check that any patches they've sent me are actually there. David.

1 0

SFBA ML Users Group Columbus Day
by byron.hale＠einfo.com 06 Oct '04

06 Oct '04

Hi All, There will be a San Francisco Bay Area ML Users Group on Monday, October 11 (Columbus Day), apparently in Fremont, CA. Although it started as OCaml, we are unsure just where our center of gravity lies, hence we are calling it "ML," at least for now. Note that Stephen Weeks (MLton) lives in this area. For further information, see: http://www.evite.com/pages/invite/viewInvite.jsp?inviteId=EEQASETVEDXJWNCZN… Best Regards, Byron Hale byron.hale(a)einfo.com

1 0

Silencing the Runtime
by bfulgham＠debian.org 05 Oct '04

05 Oct '04

Is there any way to convince PolyML to stop reporting startup information? For example, I created a child database, and overrode the "onEntry" method per the FAQ to call my "hello world" function. If I run, I still get lots of helpful data about PolyML: brent@hopper:/opt/shootout/shootout/bench/hello/tmp$ poly hello.test_dbase Poly/ML RTS version I386-4.1.3 (23:03:15 Oct 2 2004) Copyright (c) 2002 CUTS and contributors. Running with heap parameters (h=10240K,ib=2048K,ip=100%,mb=6144K,mp=20%) Mapping ./hello.test_dbase Mapping /usr/lib/poly/ML_dbase Poly/ML 4.1.3 Release hello world The standard function is OS.Process.exit I add a new runtime option "-q" for quiet, to silence some of the output (by adding some "if (! be_silent) { proper_printf.... }" stuff): brent@hopper:/opt/shootout/shootout/bench/hello/tmp$ poly -q hello.test_dbase Poly/ML 4.1.3 Release hello world The standard function is OS.Process.exit This works a bit better, but it looks like the "startupFn" still wants to report it's release value. Can I override this somehow when creating my child database? Also, can I get PolyML to stop reporting "The standard function is OS.Process.exit" when I call "PolyML.quit()" ? Thanks, -Brent

3 4

Development release?
by David.Matthews＠prolingua.co.uk 05 Oct '04

05 Oct '04

There really hasn't been much development of Poly/ML over the last year or so although I've done one or two things to it. I've also received various patches and the recent ones have made me think about this. I don't think there's enough to justify a new release. Producing a new release involves quite a bit of work for me in running the regression tests on the various platforms and building the various binaries. I feel it also involves work for people using Poly/ML and I'm thnking particularly of those using it to support Isabelle and ProofPower. It may be better to make available the latest sources on the web site as a development version. I considered making available my internal CVS server but I'm concerned about issues of security. What do people think? David.

2 1

bug in detection of tail recursive calls ?
by obua＠in.tum.de 29 Sep '04

29 Sep '04

Hi, attached is an ML program "tailrecursive.ML" that calculates !n = n * (n-1) * (n-2) * ... * 1 by rewriting. Nevertheless, it doesn't matter so much what the program does, but that calls to the function "testfac" lead to a stack overflow, although the relevant functions "lookup", "weak", "weak_last", "strong", "strong_last" are all clearly tail recursive. Running "testfac 100" succeeds, whereas evaluating "testfac 400" leads to the output below: Poly/ML RTS version I386-4.1.3 (14:28:57 Sep 30 2002) Copyright (c) 2002 CUTS and contributors. Running with heap parameters (h=10240K,ib=2048K,ip=100%,mb=6144K,mp=20%) WARNING:/usr/lib/poly/ML_dbase: Write permission denied. WARNING:/usr/lib/poly/ML_dbase: Opened for reading only. Mapping /usr/lib/poly/ML_dbase Poly/ML 4.1.3 Release > use "tailrecursive.ML"; ..... > testfac 400; calc fac in native ML calc fac by rewriting Warning - Increasing stack from 147456 to 294912 bytes Warning - Increasing stack from 294912 to 589824 bytes Warning - Increasing stack from 589824 to 1179648 bytes Warning - Increasing stack from 1179648 to 2359296 bytes Warning - Increasing stack from 2359296 to 4718592 bytes Warning - Increasing stack from 4718592 to 9437184 bytes Warning - Increasing stack from 9437184 to 18874368 bytes Warning - Increasing stack from 18874368 to 37748736 bytes Warning - Increasing stack from 37748736 to 67108860 bytes Warning - Stack limit reached - interrupting process Exception- Interrupt raised Is this a bug in Poly/ML? Does anybody know a workaround? I tried the same with Standard ML of New Jersey, 110.46, and even "testfac 7000" is unproblematic for SML/NJ. Any help with / thoughts on this would be much appreciated, Steven -- Steven Obua Technische Universit?t M?nchen Institut f?r Informatik Boltzmannstr. 3 D-85748 Garching Tel: ++49 (0)89 / 289-17328 EMail: obua(a)in.tum.de Raum: 01.11.059

2 1

Poly/ML Debugger
by rda＠lemma-one.com 26 Jul '04

26 Jul '04

I have recently been getting into using the debugger, and I must say I'm impressed. It is very nice that you get the full power of the interactive compiler in very much the right value-binding context to understand how things are inside your functions. I do have a few comments and queries though. In case any of this is platform specific, I have mainly been using it on x86 Linux with a 2.4.21 kernel. 1) The example in the documentation doesn't quite work as stated. The problem seems to be a general one: the only break-points seem to be at the head of a function (i.e., with the parameter bindings done, but not any bindings in let-expressions). When you go up the stack, values bound between the head of the function and the point of execution are not in scope. I.e., if you have something like: fun f x = let y = h x; in g y end; and break in g, when you go up to f, you can't see y (you can rerun the binding, but that may not be the right thing to do if h has side-effects). 2) If you mistype a function name in the parameter to breakIn, it doesn't cause an error (maybe this is a side-effect of a feature? it does seem to be very tolerant of the function names, e.g., you seem to be able leave off structure names and can stop in functions that aren't visible outside their structure). 3) It would be very nice indeed if you could break at points where an exception is raised. I can see that this might be a bit tricky because an awful lot of my ML code is failure-driven, so lots of exceptions get raised "unexceptionally" and you'd want a way of describing "exceptional" exceptions, In my case the ones I'm interested in are the ones that aren't going to be caught. 4) Is there are any run-time overhead in having code compiled with PolyML.Compiler.debug true? 5) ProofPower puts a wrapper around the compiler's read-eval-print loop (by calling PolyML.compiler with appropriate arguments to do the reading and printing). It would be nice if we could do the same with the debugger's read-eval-print loop. Regards, Rob.

3 6

← Newer
1
...
62
63
64
65
66
67
68
69
70
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Poly/ML