Hi,
Marnen Laibow-Koser skribis:
> On Sat, Mar 7, 2020 at 10:12 AM Ludovic Courtès wrote:
[...]
>> Could you provide a backtrace of the segfault?
>>
>
> I’m not sure how I would be able to get any more detailed debugging info
> than the logs that I posted in the GitLab issue. Have you looked
On Sat, Mar 7, 2020 at 10:12 AM Ludovic Courtès wrote:
> Hi,
>
> Marnen Laibow-Koser skribis:
>
> > I'm not sure this is a bug report yet, but it may become one. I'm having
> > what looks like a Guile segfault issue for some Mac OS Mojave (10.14)
> &g
Hello,
Le sam. 7 mars 2020 à 17:04, Ludovic Courtès a écrit :
>
> Hello,
>
> Fabrice Fontaine skribis:
>
> > guile fails to build without makeinfo:
> >
> > make[4]: Entering directory
> > '/nvmedata/autobuild/instance-7/output-1/build/host-guile-2.0.14/doc/ref'
> > MAKEINFO guile.info
> > /nvm
Hi,
Ludovic Courtès skribis:
> I have a test that runs ‘guix system build’ on this file:
>
> (use-modules (gnu)) ; 1
> (use-service-modules networking) ; 2
>
> (operating-system ; 4
> (host-name "antelop
Hello,
Fabrice Fontaine skribis:
> guile fails to build without makeinfo:
>
> make[4]: Entering directory
> '/nvmedata/autobuild/instance-7/output-1/build/host-guile-2.0.14/doc/ref'
> MAKEINFO guile.info
> /nvmedata/autobuild/instance-7/output-1/build/host-guile-2.0.14/build-aux/missing:
> lin
Hi,
Marnen Laibow-Koser skribis:
> I'm not sure this is a bug report yet, but it may become one. I'm having
> what looks like a Guile segfault issue for some Mac OS Mojave (10.14)
> users. I've been packaging 64-bit Mac builds of LilyPond, which includes
> libguil
guile fails to build without makeinfo:
make[4]: Entering directory
'/nvmedata/autobuild/instance-7/output-1/build/host-guile-2.0.14/doc/ref'
MAKEINFO guile.info
/nvmedata/autobuild/instance-7/output-1/build/host-guile-2.0.14/build-aux/missing:
line 81: makeinfo: command not found
WARNING: 'makei
Hi,
"franco@gmail.com" skribis:
> ;;Now, submitting this simple https request, you get an exception
> (http-request "https://www.google.com";)
> ice-9/boot-9.scm:1669:16: In procedure raise-exception:
> Throw to key `gnutls-error' with args `(# connessione TLS non è stata terminata in modo
Hi,
Klaus Stehle skribis:
> The file "./meta/guile.m4", which comes with guile-3.0.0, is the old
> version of guile-2.2
> Autoconf-based packages built with guile-3.0 are installed in the
> site/2.2-directories :-(
>
>
> Line 64 of "guile.m4" looks like this:
>
> _guile_versions_to_search="m4
Hi Klaus,
Klaus Stehle skribis:
> ;; The compiled program II says: "Error while printing exception".
> ;; It doesn't matter which function produces the string for the error message.
> ;; The compiled version does not work, if the message string is the returned
> ;; value of a function. The pure
Andy Wingo skribis:
> On Fri 06 Mar 2020 15:42, Ludovic Courtès writes:
>
>> Andy Wingo skribis:
>>
variable,
hashtable,
fluid,
dynamic_state,
frame,
atomic_box,
program,
vm_cont,
weak_set,
weak_table,
port
>>>
>>> No
The example below leads to a Guile 3.0.0 segfault while trying to
display a backtrace from the evaluator:
--8<---cut here---start->8---
$ cat ~/src/guile-debugging/scm_is_values-abort.scm
(use-modules (ice-9 time))
(time (ash 1 #;(expt 2 82) 4835703278458516698
On Fri 06 Mar 2020 15:42, Ludovic Courtès writes:
> Andy Wingo skribis:
>
>>> variable,
>>> hashtable,
>>> fluid,
>>> dynamic_state,
>>> frame,
>>> atomic_box,
>>> program,
>>> vm_cont,
>>> weak_set,
>>> weak_table,
>>> port
>>
>> No equal? implementation, so should hashq()
Rob Browning skribis:
> Even setting aside any security concerns, this caused tests to fail if
> you ran them as a given user and then ran them again as another user.
>
> ---
>
> It didn't look like we have anything like mkdtemp or I'd have used it
> instead. And it looks like this might apply
Andy Wingo skribis:
>> variable,
>> hashtable,
>> fluid,
>> dynamic_state,
>> frame,
>> atomic_box,
>> program,
>> vm_cont,
>> weak_set,
>> weak_table,
>> port
>
> No equal? implementation, so should hashq() instead.
Here’s a patch for these, let me know what you think!
(O
Hello,
Consider this:
--8<---cut here---start->8---
scheme@(guile-user)> (compile `(ash 1 ,(expt 2 64)) #:to 'value)
ice-9/boot-9.scm:1669:16: In procedure raise-exception:
In procedure bytevector-u32-native-set!: Argument 3 out of range: 4294967296
Entering a
Hi,
Stefan Israelsson Tampe skribis:
> Consider this source file: test.scm:
>
> (use-modules (language python def) (system syntax internal) ((oop dict)
> #:select (slask-it)))
>
> (define-syntax m
> (lambda (x)
> (syntax-case x ()
> ((_ n m y)
>(let* ((xx (syntax-expression x
Thanks very much for the report!
I think this one may be a good one for Ludovic, if I may be so bold.
Apologies for the top-post but I couldn't clip your excellent report.
Cheers,
Andy
"franco@gmail.com" writes:
> Hello,
> I installed gnutls for guile and checked the gnutls module with
Stefan Israelsson Tampe writes:
> Executing this code on guile-3.0.0:
>
> (dynamic-wind
> (lambda () (pk 'enter))
> (lambda () (catch #t
> (lambda () (throw 1))
> (lambda x (pk 'catch x) (apply throw x
> (lambda () (pk 'leave)))
>
> Leads to the output:
>
> sche
Julien Lepiller writes:
> I have a project I used to build with guile 2.2. I use the PKG_GUILE m4
> macro in my configure.ac. However, guile 3 comes with a guile.m4 whose
> PKG_GUILE only checks for 2.2, 2.0 and 1.8, so configure fails.
>
> Is this deprecated? Should I use something else to check
Hi there!
I'm not sure this is a bug report yet, but it may become one. I'm having
what looks like a Guile segfault issue for some Mac OS Mojave (10.14)
users. I've been packaging 64-bit Mac builds of LilyPond, which includes
libguile 1.8. The builds work well for myself and for
Julien Lepiller writes:
> I have a project I used to build with guile 2.2. I use the PKG_GUILE
> m4 macro in my configure.ac. However, guile 3 comes with a guile.m4
> whose PKG_GUILE only checks for 2.2, 2.0 and 1.8, so configure fails.
I use “GUILE_PKG([3.0 2.2])” in my code.
--
Ricardo
Hi,
I have a project I used to build with guile 2.2. I use the PKG_GUILE m4 macro
in my configure.ac. However, guile 3 comes with a guile.m4 whose PKG_GUILE only
checks for 2.2, 2.0 and 1.8, so configure fails.
Is this deprecated? Should I use something else to check for guile?
Thanks!
Consider this source file: test.scm:
(use-modules (language python def) (system syntax internal) ((oop dict)
#:select (slask-it)))
(define-syntax m
(lambda (x)
(syntax-case x ()
((_ n m y)
(let* ((xx (syntax-expression x))
(yy (pk 'yy (source-properties xx)))
Seconding what Brian said, I would also be happy with this solution.
Right now, guix users on aarch64 simply aren't using guile 3 because they can't
pull, so this one bug probably acts as a blocker to encountering other
potential bugs.
So even though it's not satisfactory,
Hello!
I built GNU Guix's `bootstrap-tarballs` package which includes Guile 2.2
with `guix build --target=powerpc64-linux-gnu bootstrap-tarballs` and
when I run that compiled Guile on powerpc64, it crashes.
I tried replacing the .go files with natively built ones and it works,
with the same cross
Executing this code on guile-3.0.0:
(dynamic-wind
(lambda () (pk 'enter))
(lambda () (catch #t
(lambda () (throw 1))
(lambda x (pk 'catch x) (apply throw x
(lambda () (pk 'leave)))
Leads to the output:
scheme@(guile-user)> (load "bug.scm")
;;; (enter)
;;; (catc
mentation, so should hashq() instead.
>
>> bytevector,
>> array,
>> bitvector,
>
> These have equal? implementations, and what's more, a bitvector can
> equal? an array... I think we have another bug!
>
> ;; Project 2d array as 1d array (scm_tc7_array)
>
Hello,
I installed gnutls for guile and checked the gnutls module with this
simple code:
;;Guile version 3.0 and gnutls from git
,show version
GNU Guile 3.0.0.15-ff14b7
(gnutls-version)
$6 = "3.6.12"
;;Now, submitting this simple https request, you get an exception
(http-request "https://w
equal? implementation, so should hashq() instead.
>
>> bytevector,
>> array,
>> bitvector,
>
> These have equal? implementations, and what's more, a bitvector can
> equal? an array... I think we have another bug!
>
> ;; Project 2d array as 1
d what's more, a bitvector can
equal? an array... I think we have another bug!
;; Project 2d array as 1d array (scm_tc7_array)
(define x
(make-shared-array #2b((#t #t #t)) (lambda (i) (list 0 i)) '(0 2)))
;; scm_tc7_bitvector
(define y #*111)
(equal? x y) ;; =>
Hi Rob,
Rob Browning skribis:
>>From b380102564aad053f22586eb404e99c82635a3b0 Mon Sep 17 00:00:00 2001
> From: Rob Browning
> Date: Sun, 16 Feb 2020 12:12:08 -0600
> Subject: [PATCH 1/1] Implement hashing for keywords, i.e. (hash #:x ...)
>
> Add keyword handling to (hash ...). Previously it w
On Wed, Feb 19, 2020 at 09:40:44PM +0100, Andy Wingo wrote:
> > a forum commenter has brought my attention to the fact that
> > https://www.gnu.org/software/guile/docs/ page mentions "Preview
> > Reference Manual for unreleased Guile 2.2 (development branch)"
> > and fails to mention 3.0 completely
Michael Shigorin writes:
> Hello,
> a forum commenter has brought my attention to the fact that
> https://www.gnu.org/software/guile/docs/ page mentions "Preview
> Reference Manual for unreleased Guile 2.2 (development branch)"
> and fails to mention 3.0 completely (even if it's been releas
gnu/store/h9qcvg71bmx735fsndagll9y7s72k9n9-module-import-compiled"
>> guix-system-builder )
>> […]
>> loading 'gnu/services/cups.scm'...
>> Backtrace:
>
> Apparently this bug does not occur with v3.0.0-23-g7dc90a17e¹. It may
> be that 00fbdfa7345765168e144
dule-import" "-C"
> "/gnu/store/h9qcvg71bmx735fsndagll9y7s72k9n9-module-import-compiled"
> guix-system-builder )
> […]
> loading 'gnu/services/cups.scm'...
> Backtrace:
Apparently this bug does not occur with v3.0.0-23-g7dc90a17e¹. It may
be that 0
Dear Amirouche,
The Github links don't seem to work (for me).
Kind regards,
Roel Janssen
On Tue, 2020-01-14 at 12:15 +, Amirouche wrote:
> I benchmarked Chez Scheme vs. Guile. Guile is 3 to 5 times slower
> than Chez. I attribute that mostly to C Foreign Function Interface.
>
> The applica
On Tue, Feb 18, 2020 at 12:11:19AM +0300, Michael Shigorin wrote:
> a forum commenter has brought my attention to the fact that
> https://www.gnu.org/software/guile/docs/ page mentions "Preview
> Reference Manual for unreleased Guile 2.2 (development branch)"
> and fails to mention 3.0 completely (
Hello,
a forum commenter has brought my attention to the fact that
https://www.gnu.org/software/guile/docs/ page mentions "Preview
Reference Manual for unreleased Guile 2.2 (development branch)"
and fails to mention 3.0 completely (even if it's been released
recently).
So please refer to S
Aah, you all are amazing -- thank you!! Applied and merged.
Cheers,
Andy
On Mon 17 Feb 2020 20:27, Charles Stanhope writes:
> On 2/16/20, Charles Stanhope wrote:
>> On 2/16/20, Mike Gran wrote:
>>>
>>> I can confirm that Charles's patch, plus another one line patch
>>> to define CPU_SETSIZE
On 2/16/20, Charles Stanhope wrote:
> On 2/16/20, Mike Gran wrote:
>>
>> I can confirm that Charles's patch, plus another one line patch
>> to define CPU_SETSIZE, is enough to get Guile 3.0.x to build and run
>> on my box. All tests pass except strptime in French, and the absence
>> of crypt. T
On 2/16/20, Mike Gran wrote:
> On Fri, Feb 14, 2020 at 09:46:04AM -0800, Charles Stanhope wrote:
>> Andy, I don't know if you'd want to continue this here or on
>> lightening's gitlab page, but I looked into this a little bit a few
>> minutes here and there this past weeek. The x86 "fast-call" cal
Excellent, and thank you all! I've been WIndowsless for a few weeks, but
that should change again soon.
On Sun, Feb 16, 2020 at 6:23 PM Mike Gran wrote:
> On Fri, Feb 14, 2020 at 09:46:04AM -0800, Charles Stanhope wrote:
> > Andy, I don't know if you'd want to continue this here or on
> > light
On Fri, Feb 14, 2020 at 09:46:04AM -0800, Charles Stanhope wrote:
> Andy, I don't know if you'd want to continue this here or on
> lightening's gitlab page, but I looked into this a little bit a few
> minutes here and there this past weeek. The x86 "fast-call" calling
> convention used on Windows x
(hash #:x most-postive-fixnum) hashes to the same value for all keyowrds
in at least 2.2 and 3.0. Here's one potential fix for 3.0, and I'd be
happy to adjust it for 2.2 if needed.
>From b380102564aad053f22586eb404e99c82635a3b0 Mon Sep 17 00:00:00 2001
From: Rob Browning
Date: Sun, 16 Feb 2020
Hi,
skribis:
> The link on page
> https://guix.gnu.org/blog/2018/a-packaging-tutorial-for-guix/ that redirects
> to https://www.gnu.org/software/guile/manual/en/html_node/Keywords.html
> doesn't work
The tutorial contained incorrect URLs (with “/en”). This is fixed now.
Thanks,
Ludo’.
[ re-send, used gmane to post a follow-up on the initial bug report, and
realized that this likely cannot work. Apologies if I'm wrong and this
ends up as a duplicate. ]
Andreas Rottmann writes:
> [...] I isolated the cause; the following snippet hangs on Guile 2.2
> and 3.
Andreas Rottmann writes:
> [...] I isolated the cause; the following snippet hangs on Guile 2.2
> and 3.0, while it worked as expected on 2.0:
>
> ;; --
> (import (rnrs))
>
> (let* ((p (pipe))
>(in (car p))
>(out (transcoded-port (cdr p) (make-transcoder (utf-8-cod
Hi fellow Schemers!
I was gently nudged on IRC into having a look into my Scheme code, after
many years of abandon, and found that `dorodango` (a reasonably large
body of R6RS code) hangs with Guile 2.2 and 3.0, while it worked on 2.0
(IIRC). I isolated the cause; the following snippet hangs on Gu
On 2/6/20, Charles Stanhope wrote:
> On 2/6/20, Andy Wingo wrote:
>
>> Given that John said that compilation went fine with
>> GUILE_JIT_THRESHOLD=-1, I think perhaps this problem may have been fixed
>> in the past. My suspicions are that this issue is an ABI issue with
>> lightening that could
I'm running Guile 3.0.0 and very new to Guile. Forgive me if this is
not the right place to report (or whether I should do more search,
where?, before reporting)
It seems like in r7rs mode, srfi libraries are still named in "Guile
style", (srfi srfi-1). I can't find a place in r7rs-small to spell
Den tors 13 feb. 2020 12:37Ludovic Courtès skrev:
> Yay! It’s nice to see how 7dc90a17e03045c7cd8894b14b027b845b68aa4f is
> short and clear.
>
> Thanks,
> Ludo’.
>
(You're lucky, Ludo', that we don't take that statement literally. :-))
Thanks!
>
Hi Andy,
Andy Wingo skribis:
>> However, 3.0.0 keeps the computation of ‘i’:
>>
> [...]
>> L3:
>> 53(instrument-loop 139)
>> 55(handle-interrupts)
>> 56(call-scm<-scm-uimm 5 5 1 3) at (unknown
>> file):388:11
>> 58(call-sc
With the current pdfs (https://github.com/ijp/pfds
454033f82dac7c0b0ea9e84eed1e8ed316487c78), the code below halts on an
rnrs record assertion failure with both guile-2.2 and guile-3.0, and I'm
wondering if I'm doing something wrong, if it might be a guile bug, or
if it's more
On Wed 12 Feb 2020 12:50, Ludovic Courtès writes:
> Hello!
>
> Consider this loop:
>
> (let loop ((n (expt 2 18))
> (i 1))
> (unless (zero? n)
> (loop (- n 1)
> (logior 0 (ash i 1)
>
> Guile 2.2 strips away the computation of ‘i’ (it cannot throw, has no
>
Hello!
Consider this loop:
(let loop ((n (expt 2 18))
(i 1))
(unless (zero? n)
(loop (- n 1)
(logior 0 (ash i 1)
Guile 2.2 strips away the computation of ‘i’ (it cannot throw, has no
side effects, and the result is unused):
--8<---cut here---
Hi,
a strange problem with guile-3.0.0 ...
;; (I) This one-line program shows an error message, no problem:
(error "We want to see this error message!")
;; (II) A similar program doesn't show the message, if it has been compiled:
(error (format #f "We want to see this error message!"))
tter).
>
> So I wondered if this might be a bug, or was expected behavior. It's
> also easy to work around -- just change the first define to a
> define-method.
Not sure if this might be related. With guile-3.0
(use-modules (oop goops))
(define x close)
(define-generic x)
prod
On 2/6/20, Andy Wingo wrote:
> Given that John said that compilation went fine with
> GUILE_JIT_THRESHOLD=-1, I think perhaps this problem may have been fixed
> in the past. My suspicions are that this issue is an ABI issue with
> lightening that could perhaps be reproduced by:
>
> git co http
On 06.02.20 15:07, Ludovic Courtès wrote:
Hi Jonathan,
As discussed yesterday on #guix, I tried this:
guix build guile3.0-guix --with-input=libgc@7=libgc@8
as of Guix commit 9d0dfd9a9a7c43363a4e140c20d49f119fe6f2e3. Guile 3.0.0
itself builds fine (test suite included), but the build of Gui
Hi Jonathan,
As discussed yesterday on #guix, I tried this:
guix build guile3.0-guix --with-input=libgc@7=libgc@8
as of Guix commit 9d0dfd9a9a7c43363a4e140c20d49f119fe6f2e3. Guile 3.0.0
itself builds fine (test suite included), but the build of Guix crashes
like this (on x86_64-linux-gnu):
-
On Mon 20 Jan 2020 18:22, Mike Gran writes:
> On Mon, Jan 20, 2020 at 11:38:35AM -0500, John Cowan wrote:
>> Yes, gladly, but I don't know how to get one in this context. Do I need to
>> add some flags to the Makefile, and if so, where? (It's a twisty maze of
>> passages, all different.) . Note
; > > all. This is what I get when I specify ulimit -c unlimited and rebuild:
> > > [...]
> >
> > Please see my previous mail on how to get a real core dump on cygwin
> > https://debbugs.gnu.org/cgi/bugreport.cgi?bug=39118#28
>
>
> Okay, I looked at tha
t; > [...]
>
> Please see my previous mail on how to get a real core dump on cygwin
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=39118#28
Okay, I looked at that page. However, Cygwin's dumper requires you to know
the Windows PID of the process to dump. Clearly it is intended for a
The file "./meta/guile.m4", which comes with guile-3.0.0, is the old
version of guile-2.2
Autoconf-based packages built with guile-3.0 are installed in the
site/2.2-directories :-(
Line 64 of "guile.m4" looks like this:
_guile_versions_to_search="m4_default([$1], [2.2 2.0 1.8])"
It shou
The link on page https://guix.gnu.org/blog/2018/a-packaging-tutorial-for-guix/
that redirects to
https://www.gnu.org/software/guile/manual/en/html_node/Keywords.html doesn't
work
Hi,
The link on page https://www.gnu.org/software/guile/libraries/ that redirect to
http://home.gna.org/guile-dbi/guile-dbi.html doesn't work
ump on cygwin
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=39118#28
>> On Sat, Jan 25, 2020 at 8:51 AM Ludovic Courtès wrote:
>>
>>> That I understand. However, I was asking for the backtrace of the crash
>>> on Cygwin when JIT is enabled. Could you grab it?
#v+
Just for the record: Ludo added libgc-8 in
69961ac3b9db2dbb99abb5c45ff6be3a9c01b5de on master. It's not yet used,
so we need to replace libgc-7.6 with it and see how it goes...
t the the manual says this:
If symbol was previously bound to a Scheme procedure (or
procedure-with-setter), the old procedure (and setter) is incorporated
into the new generic function as its default procedure (and setter).
So I wondered if this might be a bug, or was expected behavior.
Aaaand... Cygwin doesn't do core dumps. Under the skin it's WIndows, after
all. This is what I get when I specify ulimit -c unlimited and rebuild:
Exception: STATUS_ACCESS_VIOLATION at rip=0055A8B1B25
rax= rbx=FF90 rcx=FF90
rdx=0034964A rsi=0700
I think I found a gc leak in guile 3.0
Isn't it so that so the continuation keep a copy of the stack. The issue is
that in the stack a raw integer or float may be present and so the gc
properties is less then ideal as those may be interpreted as pointers by
the GC and lead to parts of the heap bei
ing users to create\ngames using Python as well as C++.
>>
>> ->
>>
>> is a multi-platform isometric game engine. Python bindings are
>> included allowing users to create games using Python as well as C++.
>>
>>
>> I believe this is a bug in
platform isometric game engine. Python bindings are
> included allowing users to create games using Python as well as C++.
>
>
> I believe this is a bug in Guile, but it could also be a problem with
> the texinfo markup.
Fixed in Guile commit ff14b77ff527f297438b83614db0c1d56322ec4
-- Forwarded message -
From: Stefan Israelsson Tampe
Date: Mon, Jan 27, 2020 at 8:38 PM
Subject: Re: GNU Guile 3.0.0 released
To: guile-devel , Andy Wingo
This does not look right (for guile 3.0.0)
-
;b.scm:
(define-module (b)
#:export (%f g))
Hi,
Guiles reference manual mentions a procedure program-bindings in (system
vm programs) in the "Compiled Procedures" node. It is missing however on
guile-3.0 and a quick grep over Guiles sources shows no result apart
from the documentation.
The documentation should probably be removed unless I mi
On Sat, Jan 25, 2020 at 8:51 AM Ludovic Courtès wrote:
> That I understand. However, I was asking for the backtrace of the crash
> on Cygwin when JIT is enabled. Could you grab it?
>
1. The wisdom of the Internet has not been able to figure out how to
generate a core dump on MacOS 10.15.2 (Ca
John Cowan skribis:
> Both Cygwin and MacOS crash in pretty much the same way. By disabling the
> JIT, I was able to get the Cygwin build to run to completion.
That I understand. However, I was asking for the backtrace of the crash
on Cygwin when JIT is enabled. Could you grab it?
Thanks in
t: Friday January 24 2020 9:36:59AM
Subject: bug#39118: Segfault while building on 64-bit Cygwin
Both Cygwin and MacOS crash in pretty much the same way. By disabling
the JIT, I was able to get the Cygwin build to run to completion. On
MacOS with --disable-jit, however, I am now getting an entir
Hello!
While building the “guix-system.drv” derivation on AArch64, I got this
crash (not fully deterministic but quite frequent). Here the
finalization thread gets a wrong-type-arg in ‘scm_i_weak_car’ (i.e.,
accessing a one-element weak vector):
--8<---cut here---start---
at 3:35 PM Ludovic Courtès wrote:
> Hi,
>
> John Cowan skribis:
>
> > Thanks. Unfortunately, the standard recipe for making core dumps on Mac
>
> This bug report is about Cygwin, not macOS, right? :-)
>
> Ludo’.
>
Hi,
John Cowan skribis:
> Thanks. Unfortunately, the standard recipe for making core dumps on Mac
This bug report is about Cygwin, not macOS, right? :-)
Ludo’.
Hello,
DongChan LEE skribis:
> I have a problem to configure a Guile 2.2.6 on my environment.
>
> (I downloaded full source code through https://ftp.gnu.org/gnu/guile/)
>
> And I extracted the compressed file into this path and configured with below
> parameters.
>
> - /user/dc.lee/GUILE
>
>
HI All:
My 'make check' fails after building guile 3.0.0 on Ubuntu 18.04.3 LTS.
I built the system with GCC 7.4.0 with dependencies as:
Boehm gc 8.0.4
GMP 6.1.2
libffi 3.3
libtool 2.4.6
libunistring 0.9.10
pkg-config 0.29.2
These dependencies were built from scratch and installed to /usr/local.
I'm no longer talking about Cygwin (which builds fine without JIT). I'm
now talking about MacOS Catalina, which needs a core dump to debug, but on
which nobody seems to know how to enable core dumps.
On Tue, Jan 21, 2020 at 1:41 PM szgyg wrote:
> On Tue, Jan 21, 2020 at 10:01:58AM +0100, Ludovi
Thanks. Unfortunately, the standard recipe for making core dumps on Mac
(put "limit core unlimited" into /etc/launchd.conf and reboot, make sure
/cores is writable, set ulimit -c unlimited) seem to actually enable them
on MacOS Catalina (10.15.2). I have tested with SIGQUIT and SIGSEGV on
running
On Tue, Jan 21, 2020 at 10:01:58AM +0100, Ludovic Courtès wrote:
> but before that you’d run
> “ulimit -c unlimited” in that shell to make sure there’s a core dumped
> when it crashes.
This won't work on cygwin. If you want a core dump, you should use the
dumper tool, as described here
https://cyg
The configuration process misses incompatible readline and sed.
A wrong readline is found at the end of the make process and a wrong sed is
found during the make install process.
Both should be discovered during configuration.
See the irc exchange on Jan. 21-22 with brandelune.
Jean-Christophe
Elisp symbolp does not think nil is a symbol, which it is in Emacs Elisp.
Fixing this should not affect Scheme's symbol? predicate.
The writer in modules/language/elisp/spec.scm specifies Scheme's write as
the REPL writer, so that entering nil at the Elisp prompt prints out #nil,
which is meaningless to Elisp users. Likewise, (print nil) does the same
thing. A proper Elisp writer is needed.
Hello,
Ricardo Wurmus skribis:
> The module (rnrs conditions (6)) exports &assertion but renames the
> imported &assertion-failure to &assertion-violation (not &assertion).
> Programs using &assertion from (rnrs conditions) fail with an unbound
> variable error.
>
> Using &violation instead of &
Hi Rob,
Rob Browning skribis:
> Even setting aside any security concerns, this caused tests to fail if
> you ran them as a given user and then ran them again as another user.
Oops, indeed.
> It didn't look like we have anything like mkdtemp or I'd have used it
> instead. And it looks like t
Hello,
John Cowan skribis:
> Yes, gladly, but I don't know how to get one in this context.
You would unpack, configure, and build like you did before (with JIT
enabled, so as to reproduce the crash), but before that you’d run
“ulimit -c unlimited” in that shell to make sure there’s a core dumpe
Even setting aside any security concerns, this caused tests to fail if
you ran them as a given user and then ran them again as another user.
---
It didn't look like we have anything like mkdtemp or I'd have used it
instead. And it looks like this might apply to, and it would be nice
to have s
The module (rnrs conditions (6)) exports &assertion but renames the
imported &assertion-failure to &assertion-violation (not &assertion).
Programs using &assertion from (rnrs conditions) fail with an unbound
variable error.
Using &violation instead of &assertion works.
--
Ricardo
On Mon, Jan 20, 2020 at 11:38:35AM -0500, John Cowan wrote:
> Yes, gladly, but I don't know how to get one in this context. Do I need to
> add some flags to the Makefile, and if so, where? (It's a twisty maze of
> passages, all different.) . Note that this *is* a build with JIT enabled;
> when I
Ludovic Courtès skribis:
> Unfortunately I’m unable to reproduce the bug outside Guix’s build
> environment, even with ASLR disabled (what guix-daemon does).
I finally managed to reproduce it with from the failed-build tree:
rm -vf
bootstrap/language/cps/{slot-allocation,specialize-n
Yes, gladly, but I don't know how to get one in this context. Do I need to
add some flags to the Makefile, and if so, where? (It's a twisty maze of
passages, all different.) . Note that this *is* a build with JIT enabled;
when I disable it using the env variable, there are no errors and 3.0.0
wor
Hi John,
John Cowan skribis:
> Guile 2.9.9, like .8 and .7, does not build on Cygwin (64 bit). Configure
> runs without error, but make crashes with this (truncated to just the tail):
>
> Making all in bootstrap
> make[2]: Entering directory
> '/cygdrive/c/Users/rr828893/Downloads/guile-2.9.9/b
R\001",
__align = 95281925316411917}, sleep_pipe = {525, 22184560},
dynamic_state = 0xa, dynstack = {base = 0x0, top = 0x5, limit = 0x789780},
continuation_root = 0x2db7da0c,
continuation_base = 0xdebc98, base = 0x20d, jit_state = 0xdede20}
--8<---cut here---end--
1401 - 1500 of 6094 matches
Mail list logo
