Poly/ML December 2004

polyml@lists.polyml.org

4 participants
5 discussions

Seg. fault
by m.a.ellis＠ncl.ac.uk 14 Apr '05

14 Apr '05

FYI, Lest anyone be planning an upgrade, I get segmentation faults on PolyML startup using Linux 2.6.9 (using PolyML as distributed with Isabelle). Maybe it's just me though. 2.6.8.1 seems fine though. Martin

6 9

addresses.h for linux 2.6.9
by Martin.vGagern＠gmx.net 21 Dec '04

21 Dec '04

The following works for me: diff -ru polyml-4.1.3/driver/addresses.h polyml/driver/addresses.h --- polyml-4.1.3/driver/addresses.h 2002-06-18 20:47:45.000000000 +0200 +++ polyml/driver/addresses.h 2004-12-21 10:42:36.481444760 +0100 @@ -267,10 +267,10 @@ and 0x10000000 in later ones. It seems that mmap without a fixed address (and so malloc) maps at upwards of 0x40000000. These should be reasonable. DCJM 29/11/01. */ -#define LOCAL_IBOTTOM Words(0x60000000) -#define LOCAL_ITOP Words(0xa8000000) -#define LOCAL_MBOTTOM Words(0xa8000000) -#define LOCAL_MTOP Words(0xb8000000) +#define LOCAL_IBOTTOM Words(0x50000000) +#define LOCAL_ITOP Words(0x98000000) +#define LOCAL_MBOTTOM Words(0x98000000) +#define LOCAL_MTOP Words(0xa8000000) /* 1.1 Gbytes for immutable, 256Mbytes for mutable. */ /* This leaves 0xb8... - 0xbf... for the C stack. (i.e. 128 Mbytes) */

2 1

Segmentation fault
by berghofe＠in.tum.de 13 Dec '04

13 Dec '04

Hello, the attached ML file causes Poly/ML 4.1.3 to crash with a segmentation fault under Linux version 2.4.21-243-smp4G. Any help would be greatly appreciated. Greetings, Stefan -- Dr. Stefan Berghofer E-Mail: berghofe(a)in.tum.de Institut fuer Informatik Phone: +49 89 289 17328 Technische Universitaet Muenchen Fax: +49 89 289 17307 Boltzmannstr. 3 Room: 01.11.059 85748 Garching, GERMANY http://www.in.tum.de/~berghofe

2 2

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

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