Poly/ML

polyml@lists.polyml.org

2 participants
711 discussions

Segmentation Fault When Porting
by jrtc27＠jrtc27.com 21 Jan '16

21 Jan '16

Hi, I?ve been trying to port Poly/ML to mips and IBM?s S/390 (the 64-bit version, often referred to as s390x). For both, I tried just adding an extra case in configure.ac, along with corresponding HOSTARCHITECTURE macros and cases in libpolyml/elfexport.cpp. However, these all seem to segfault when polyimport is run when building (both with 5.5.2 and git commit ee26375, "Merge branch ?PICTest?"). I can?t seem to get a meaningful stack trace out of the mips segfault, but it crashes just after ?Use: basis/Socket.sml? is printed. However, on s390x, it crashes before anything is printed, and valgrind gave me the following (with no errors before this point) when running ee26375?s polyimport: ==16138== Thread 3: ==16138== Invalid read of size 8 ==16138== at 0x489EA50: Offset (globals.h:315) ==16138== by 0x489EA50: GetConstSegmentForCode (globals.h:344) ==16138== by 0x489EA50: GetConstSegmentForCode (globals.h:350) ==16138== by 0x489EA50: ConstPtrForCode (globals.h:355) ==16138== by 0x489EA50: buildStackList(TaskData*, PolyWord*, PolyWord*) (run_time.cpp:413) ==16138== by 0x489EC87: exceptionToTraceException(TaskData*, SaveVecEntry*) (run_time.cpp:471) ==16138== by 0x48AC9ED: IntTaskData::SwitchToPoly() (interpret.cpp:877) ==16138== by 0x48ACC33: IntTaskData::EnterPolyCode() (interpret.cpp:1428) ==16138== by 0x489324D: NewThreadFunction(void*) (processes.cpp:1128) ==16138== by 0x48E591D: start_thread (pthread_create.c:335) ==16138== by 0x4C8CEA9: ??? (in /lib/s390x-linux-gnu/libc-2.21.so) ==16138== Address 0xe000000005ab5b38 is not stack'd, malloc'd or (recently) free'd ==16138== ==16138== ==16138== Process terminating with default action of signal 11 (SIGSEGV) ==16138== Access not within mapped region at address 0xE000000005AB5000 ==16138== at 0x489EA50: Offset (globals.h:315) ==16138== by 0x489EA50: GetConstSegmentForCode (globals.h:344) ==16138== by 0x489EA50: GetConstSegmentForCode (globals.h:350) ==16138== by 0x489EA50: ConstPtrForCode (globals.h:355) ==16138== by 0x489EA50: buildStackList(TaskData*, PolyWord*, PolyWord*) (run_time.cpp:413) ==16138== by 0x489EC87: exceptionToTraceException(TaskData*, SaveVecEntry*) (run_time.cpp:471) ==16138== by 0x48AC9ED: IntTaskData::SwitchToPoly() (interpret.cpp:877) ==16138== by 0x48ACC33: IntTaskData::EnterPolyCode() (interpret.cpp:1428) ==16138== by 0x489324D: NewThreadFunction(void*) (processes.cpp:1128) ==16138== by 0x48E591D: start_thread (pthread_create.c:335) ==16138== by 0x4C8CEA9: ??? (in /lib/s390x-linux-gnu/libc-2.21.so) ==16138== If you believe this happened as a result of a stack ==16138== overflow in your program's main thread (unlikely but ==16138== possible), you can try to increase the size of the ==16138== main thread stack using the --main-stacksize= flag. ==16138== The main thread stack size used in this run was 8388608. (the ??? for libc is because valgrind does not yet understand compressed debug info; I removed a whole load of warnings to that effect) Have you ever come across anything like this? Do you have any thoughts for where to start with hunting this down? Regards, James Clarke

2 11

Foreign calls not working after loadState in new session
by phil.clayton＠lineone.net 19 Jan '16

19 Jan '16

After loading an existing state in a fresh session, I find that previously defined calls to C functions (saved in the state) crash the session if (and only if) the foreign call was called in an earlier session before the state was saved. I can supply an example if necessary. After investigating, it is actually malloc that is failing in the calls. Surprisingly, the very first malloc in the session finds an existing address. As freeList is emptied by PolyML.onEntry presumably freeList is being restored by loadState. Does that sound like an issue? I would expect that the freeList state is untouched by loadState. Phil

2 3

Negative offset for getX and setX functions in Foreign.Memory
by phil.clayton＠lineone.net 18 Jan '16

18 Jan '16

The functions getX and setX in Foreign.Memory take an offset as a Word.word. I'm finding that it is possible to have a negative offset by negating the word offset, e.g. get8 (p, ~ 0w1) Is that guaranteed work generally? Given that Word.wordSize = 63 SysWord.wordSize = 64 I wouldn't have expected this to work for get8/set8 but it does. Phil P.S. My efforts to inspect the source didn't get far as these functions go straight to run-time calls and I'm not familiar with internal representations in Poly/ML...

2 3

Type inference issue using signature constraint
by phil.clayton＠lineone.net 12 Jan '16

12 Jan '16

I have an example where a module is type checking fine even though I have introduced a type error into it! I've reduced it down to a small example. It looks like there is a problem using type constraints from a signature where the signature is also required to resolve record components. See attached example for details. Phil

1 0

addPrettyPrinter type security
by rda＠lemma-one.com 11 Jan '16

11 Jan '16

PolyML.addPrettyPrinter checks its printArgTypes parameter carefully when you are installing a pretty-printer for a polymorphic type. As far as I can see it guarantees type security for polymorphic types. However, when you install a pretty-printer for a monomorphic type, the parameter isn't checked at all. E.g., the following code doesn't result in any error messages and ends by crashing poly. datatype MONO = Mono of int; fun pp_mono1 _ (i : int) (Mono j) = ( PolyML.PrettyString (Int.toString (i + j)) ); PolyML.addPrettyPrinter pp_mono1; Mono 42; (* Prints "val it = 42: MONO" - apparently i was 0 *) fun pp_mono2 _ (r : int ref) (Mono _) = ( PolyML.PrettyString (Int.toString (!r)) ); PolyML.addPrettyPrinter pp_mono2; Mono 42; (* Crashes *) Shouldn't processArgTypes be required to have type unit when defining a pretty-printer for a monotype? The patch below implements this check and tries to improve the error message (which is already a bit misleading if you get something wrong for a type with more than one parameter). Regards, Rob. diff --git a/mlsource/MLCompiler/VALUE_OPS.ML b/mlsource/MLCompiler/VALUE_OPS.ML index 1535d4f..9e00f0d 100644 --- a/mlsource/MLCompiler/VALUE_OPS.ML +++ b/mlsource/MLCompiler/VALUE_OPS.ML @@ -958,8 +958,8 @@ struct val typeVars = List.tabulate(arity, fn _ => mkTypeVar (0, false, true, false)) val tupleType = case typeVars of - [] => (* No arg so we can have anything here. *) - mkTypeVar (generalisable, false, false, false) + [] => (* No arg so must have unit. *) + unitType | [arg] => mkFn arg (* Just a single function. *) | args => mkProductType(List.map mkFn args) val addPPType = mkFunctionType(argPrints, mkFunctionType(installType, pretty)) @@ -970,7 +970,7 @@ struct in checkPPType(addPPType, testType, "addPrettyPrint", lex, loc, fn () => - PrettyString "addPrettyPrint element functions must have type 'a * int -> pretty") + PrettyString "addPrettyPrint element functions must have type 'a * int -> pretty, 'b * int -> pretty, ... with one function for each type parameter") end; (* Only report the error when the function is run. Because addPrettyPrint is

2 1

Towards Poly/ML 5.6
by David.Matthews＠prolingua.co.uk 09 Jan '16

09 Jan '16

I've updated the github repository with pre-built compilers for 5.6 Release. This is now the release candidate. Unless there are any significant problems this will be released in the next few weeks. Best wishes for 2016, David

8 18

5.6 failures on OSX
by Michael.Norrish＠nicta.com.au 08 Jan '16

08 Jan '16

Our regression testing from poly's master branch with sources that are fine on 5.5.2 is showing repeated "random" failures on OSX. You can see the build history at https://travis-ci.org/HOL-Theorem-Prover/HOL/builds (ignore the k11-release-prep branch failures). In all of the recent failures of HOL's master, you'll see that it is the "GITPOLY" build on OSX failing. The GITPOLY build on Linux is fine. Unfortunately, the failures are happening at different times in the build. The only thing they seem to have in common is that there is a test (using OS.Process.isSuccess) of the result of another execution ultimately set up with OS.Process.system. The output even somewhat suggests that the child process terminated successfully; could it be that the return code is being randomly mis-interpreted? Michael ________________________________ The information in this e-mail may be confidential and subject to legal professional privilege and/or copyright. National ICT Australia Limited accepts no liability for any damage caused by this email or its attachments.

2 2

polyml mailing list not searchable by search engines
by artella.coding＠googlemail.com 28 Dec '15

28 Dec '15

For example : https://encrypted.google.com/search?as_q=&as_sitesearch=http%3A%2F%2Flists.… I personally think it would be better to have the mailing list searchable, either by allowing search engines to have access or having a built in site search. Thanks

1 0

Various changes
by David.Matthews＠prolingua.co.uk 20 Nov '15

20 Nov '15

There have been a number of changes added to the git repository over the last weeks and months. This an almost certainly incomplete list. I've tried to include changes that have come up as queries on the mailing list. Added loadHierarchy to PolyML.SavedState. This takes a list of the file names of saved states in order from grandparent, parent to child, and loads them. It functions the same way as loadState except that it allows the parent paths to be specified. Types in structures with opaque signatures are now printed as "?" rather than the print function being inherited. In the debugger, pressing control-C to the debug> prompt returns to the top-level. Actually, what happens is that break-points are disabled and the Thread.Thread.Interrupt exception is raised in the debuggee so it has a chance to clear up. If the debuggee actually catches the interrupt exception then it may not actually return to the top level. There's also a "locals" function in PolyML.Debug to display the local variables. When compiling a file with "use", PolyML.getUseFileName returns the current file name. The floating point precision is now set to 64-bits to avoid inconsistencies depending on whether an intermediate floating point value has been kept in a register or saved into memory. The PolyML.NameSpace structure has been reorganised to split out functions related to the various binding classes into separate sub-structures. The aim is to wrap up the current changes into a new release, probably 5.6 rather than 5.5.3 since there are quite a few changes. That will probably be over the next month or two. David

2 1

loadModule
by David.Matthews＠prolingua.co.uk 10 Nov '15

10 Nov '15

Some new functions have been added to PolyML.SaveState to support "modules". A module is a collection of bindings, primarily structures, signatures and functors, that can be saved and later reloaded. It's mainly aimed at those packaging up binary distributions since a module can only be reloaded into the same binary that exported it, much as with saved states. PolyML.SavedState.savedModule takes a file name and names of structures, signature and functors, together with an optional "on-start-up" function and writes them out as a package. PolyML.SavedState.loadModule takes a name and loads the module. When the module is loaded the "on-start-up" function is executed and the structures, signatures and functors are added to the top-level name space. The module name can either be a file path if it contains a directory separator e.g. ./foo or it is looked up in the path given by POLYMODPATH. There are lower level functions in SavedState that can be used to include values, type constructors and even infix bindings in a module and to import a module into a name space other than the default top-level. The idea is to provide a way for extensions to be packaged up for Poly/ML. There are a number of features that it might be nice to provide but aren't part of the core system. An example would be the Windows GUI modules but I'm sure there are others. I hope it would also encourage contributions. David

1 0

← Newer
1
...
19
20
21
22
23
24
25
...
72
Older →

Jump to page:

2026

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