GNU libsigsegv 2.11 is released

Hi, GNU libsigsegv 2.11 is released. You find the download link at the homepage https://www.gnu.org/software/libsigsegv/ New in 2.11: * Added support for catching stack overflow on Linux/SPARC. * Provide a correct value for SIGSTKSZ on 64-bit AIX and on HP-UX. The one defined by these systems

Re: new clisp packages

Two things about the clisp 2.49.60 release: 1) It MUST be configured with --enable-portability. Without it, currently there are no guarantees that it will build and run without crashes, on any platform. This option disables a number of optimizations, but has shown good succes

Re: continuous integration testing for clisp

Hello Peter, > Debian has autopkgtest [1] and CI [2] to test packages now. Do you want me to > run ‘make test’ as a part of these efforts on clisp? Is there perhaps a better > alternative? I don't know what 'make test' is. But like any GNU program, clisp has a "make check" target [1] that you can

Re: new clisp packages

The new 2.49.60 release should probably fix a couple of bugs: * https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=385490 If clisp uses libffcall-1.13 and enables the FFI on all platforms, this should be fixed. * https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=478000 Try with --enable-port

Bug#886986: please remove bump-fasl-loader-version.patch

Hi Norbert, > thanks for your email and your explanations. I am not clisp packager, > but TeX Live (upstream and Debian) maintainer and thus also xindy > maintainer. I appreciate this work that you do. Nevertheless, your view of clisp .mem file does not match reality: 1) The error "initializatio

Bug#886986: please remove bump-fasl-loader-version.patch

Sébastien Villemot wrote: > The right solution would be to extract the > hash for the .mem format when compiling clisp, and then turn it into a virtual > package (like "clisp-mem-", pretty much like we do for FASL version > format). Then, when xindy is compiled, it would acquire the dependency on t

Bug#886986: please remove bump-fasl-loader-version.patch

Norbert Preining wrote: > this is the way the build process is set up by the upstream author, and > rewritting the whole build and distribution process *independently* from > upstream xindy is not an option AFAIU, the "virtual package with a hash code in its name" concept, proposed by Sébastien, i

Bug#886986: please remove bump-fasl-loader-version.patch

Sébastien Villemot wrote: > > 1) Will the package manager report a conflict? > > Yes. > > > 2) Will the package manager propose, as solution of this conflict, to > > install > > another binary package for xindy? Or will it only propose to remove > > xindy? > > Only two options will be

GNU libsigsegv 2.12 is released

Hi, GNU libsigsegv 2.12 is released. You find the download link at the homepage https://www.gnu.org/software/libsigsegv/ New in 2.12: * Added support for catching stack overflow on Hurd/i386. * Added support for catching stack overflow on Haiku. * Corrected distinction between stack overflow a

Re: GNU libsigsegv 2.12 is released

Hi Sébastien, > Note that the following patch is applied on top of the upstream sources, it is > needed for cross-compiling the arm64 binary: > > > https://salsa.debian.org/common-lisp-team/libsigsegv/blob/master/debian/patches/aarch64-stack-direction.patch How come that it is needed? 'aarch64

GNU clisp 2.49.90 available for beta-testing

Hi, GNU clisp 2.49.90 is released. The download location is https://haible.de/bruno/gnu/clisp-2.49.90.tar.bz2 New in this beta release: * This is the first release since 2.33.2 that is supported on a wide range of platforms: Operating system | CPU/ISA| ABIs -+---

Re: GNU clisp 2.49.90 available for beta-testing

PS: With this release, for best performance you should _remove_ the option --enable-portability (line 19 in 'rules'). Bruno ___ pkg-common-lisp-devel mailing list pkg-common-lisp-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mail

Re: GNU clisp 2.49.90 available for beta-testing

Sébastien Villemot wrote: > I gave it a try, but it fails to build on a plain Debian unstable/amd64 > system, > with: > > gcc -I/tmp/clisp-2.49.90/src/gllib -g -O2 -no-integrated-cpp -W -Wswitch > -Wcomment -Wpointer-arith -Wreturn-type -Wmissing-declarations -Wimplicit > -Wno-sign-compare -Wno

Re: GNU clisp 2.49.90 available for beta-testing

Hi Sébastien, Thanks a lot for these build reports! > More precisely, the status on release architectures is the following: > - amd64: ok > - arm64: fails to generate lisp image (memory mapping issue) Please use the attached memory-map-arm64.diff. > - armel: lisp image generated, but fails to c

GNU libffcall 2.1 is released

Available at https://ftp.gnu.org/gnu/libffcall/libffcall-2.1.tar.gz New in 2.1: * Added support for the following platforms: (Previously, a build on these platforms failed.) - arm: Linux with PIE-enabled gcc. - x86_64: Solaris 11.3. - OpenBSD 6.1. - HardenedBSD 10 and 11. * Fixed a b

Re: GNU clisp 2.49.90 available for beta-testing

Hi Sébastien, > I made a new upload incorporating your patches: > > https://buildd.debian.org/status/package.php?p=clisp&suite=experimental And I made a new prerelease: https://haible.de/bruno/gnu/clisp-2.49.92.tar.bz2 It incorporates the memory-map patches, adds memory-map patches also for

Re: GNU libffcall 2.1 is released

Hi Sébastien, > Thanks, I updated the package. It went fine, except on sparc64 where it failed > to build (while it worked for 2.0, though I am not sure that the regression > comes from a change in ffcall): > > > https://buildd.debian.org/status/fetch.php?pkg=ffcall&arch=sparc64&ver=2.1-1&stamp

Re: sigsegv on s390 only giving start address of page in segv handler

Hi Christoph, When you wrote to you didn't remove the "antispam" words from the address. > libsigsegv doesn't cope well with s390 at the moment. This is caused > by the fact, that linux masks the address for sigsegv: > > mm/fault.c:#define __FAIL_ADDR_MASK 0x7000 > > So the last 12 b

Re: sigsegv on s390 only giving start address of page in segv handler

ses libsigsegv. So I'm applying this patch. Find in http://www.haible.de/bruno/gnu/libsigsegv-2.10-pre1.tar.gz a new prerelease. Can you please test how it works on a Linux/S390 system, and whether clisp then builds and runs fine? Bruno 2011-03-13 Bruno Haible Supp

Re: sigsegv on s390 only giving start address of page in segv handler

ooo > `-__|__-'8 8 8 8 8 > |8 o 8 8 o 8 8 > --+-- o 8oo ooo8ooo o 8 > > Welcome to GNU CLISP 2.49 (2010-07-07) <http://clisp.cons.org/> > > Cop

Re: [bug-libsigsegv] Re: sigsegv on s390 only giving start address of page in segv handler

Heiko Carstens wrote: > You would have to perform instruction decoding to figure out what was the > exact failing address. Not really a thankful job. This is done in libsigsegv and Boehm GC for m68k, PowerPC, and Alpha processors (see [1][2][3][4]) already. Why not also for s390 and s390x? Or eve

Re: [bug-libsigsegv] Re: sigsegv on s390 only giving start address of page in segv handler

Christian Borntraeger wrote: > I even think that this cannot be fully solved by looking at the instruction, > e.g. you cannot tell which access triggered the fault for instruction with > two memory accesses (mvc) in the same page. Sure you can. If it's a "read" fault (i.e. the page has no readabl

Re: [bug-libsigsegv] Re: sigsegv on s390 only giving start address of page in segv handler

Martin Schwidefsky wrote: > Even with the access-exception-fetch/store-indication facility you'll find > on the latest machine it is not possible to distinguish read from write > faults in all cases ... On older machines the TEID does not carry an > indication if the page translation exception has

Re: [bug-libsigsegv] Re: sigsegv on s390 only giving start address of page in segv handler

Christian Borntraeger wrote: > Can you give some insights about the other use cases? Userspace page faults > can > be handled just fine with the page address (I have done that for the s390x > port of valgrind). Would a "works most of the time but might return the page > address in 10% of the cases

Re: sigsegv on s390 only giving start address of page in segv handler

Hi Christoph, On 2011-03-13, you reported that with the Linux/S390 specific modifications to libsigsegv clisp did not yet work correctly. I proposed a patch that ought to fix this: Did you have time to test this patch? I wou

Re: sigsegv on s390 only giving start address of page in segv handler

Hi Christoph, > Using the -pre libsigsegv I can build clisp fine and it appears to > be basically working -- playing around doesn't result in any obvious > problems. However `make check` is segfaulting. I've attached output of > make check. Thanks for the testing. The segfault appears to be r