bug#59874: Segfault from string-ref with negative 'k'

HI, On +2022-12-07 11:29:28 +0100, Ricardo Wurmus wrote: > Thank you for reporting this bug. > > > i noticed that if i, on my system, run "guile" from a shell and then type > > into the command prompt that appears, > > > > (string-ref "a string

bug#59321: ice-9's open-input-pipe is unexpectedly slow on some systems

Hi, Andrew Whatson skribis: > Playing with the wip-posix-spawn branch, it has the same slowdown > (actually a bit worse). I've updated the "/proc/self/fd" fast-path > patch for posix_spawn, please find attached. Ooh that’s perfect, thank you. I’ll apply it once we’ve sorted out remaining issu

bug#59321: ice-9's open-input-pipe is unexpectedly slow on some systems

Ludovic Courtès wrote: > > Andrew Whatson skribis: > > > We also need equivalent functionality around SOCK_CLOEXEC. It seems > > this is implemented for ‘accept’, but not ‘socket’ or ‘socketpair’. > > It’s possible to use SOCK_CLOEXEC with ‘socket’ and ‘socketpair’ > already, as in: > > (socke

bug#49686: Confusing presence of #f in error message

This seems to have been fixed, probably in eb5ecf4944cd646341f7e47dda5396cf96a4b8a3. OpenPGP_signature Description: OpenPGP digital signature

bug#59874: Segfault from string-ref with negative 'k'

Hello, This is the same bug as https://debbugs.gnu.org/cgi/bugreport.cgi?bug=58154 <https://debbugs.gnu.org/cgi/bugreport.cgi?bug=58154> which is fixed in git (http://git.savannah.gnu.org/gitweb/?p=guile.git;a=commitdiff;h=c0004442b7691f59a0e37869ef288eb26382ad9e <http://git.savanna

bug#59874: Segfault from string-ref with negative 'k'

Thank you for reporting this bug. > i noticed that if i, on my system, run "guile" from a shell and then type > into the command prompt that appears, > > (string-ref "a string" -1) > > guile appears to hang for a few seconds or so, and then prints the messa

bug#59874: Segfault from string-ref with negative 'k'

On Wed, Dec 07, 2022 at 08:50:09AM +0100, rose gibson via Bug reports for GUILE, GNU's Ubiquitous Extension Language wrote: > hi, > > i noticed that if i, on my system, run "guile" from a shell and then type > into the command prompt that appears, > > (str

bug#59874: Segfault from string-ref with negative 'k'

hi, i noticed that if i, on my system, run "guile" from a shell and then type into the command prompt that appears, (string-ref "a string" -1) guile appears to hang for a few seconds or so, and then prints the message "Segmentation fault (core dumped)". i'm not really sure if this report is w

bug#52835: [PATCH 0/2] Fix spawning a child not setting standard fds properly

Hi Josselin, Sorry for taking so long to come back to you. I think this is great work! I pushed it as ‘wip-posix-spawn’ so others can give it a try. Josselin Poiret skribis: > * libguile/posix.c (renumber_file_descriptor, start_child, > scm_piped_process): Remove functions. > (scm_port_to_fd_

bug#59647: [PATCH] Fix typos in docstrings.

* libguile/boolean.c (scm_not): Fix typo. (scm_boolean_p): Fix typo. --- libguile/boolean.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/libguile/boolean.c b/libguile/boolean.c index e8370331f..930001a89 100644 --- a/libguile/boolean.c +++ b/libguile/boolean.c @@

bug#59646: [PATCH v2] Add short command for locals debug command.

--- module/system/repl/command.scm | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/module/system/repl/command.scm b/module/system/repl/command.scm index 0024fd165..d7257b5a1 100644 --- a/module/system/repl/command.scm +++ b/module/system/repl/command.scm @@ -61,7 +61,7 @@

bug#59646: [PATCH] Add short command for locals debug command.

--- module/system/repl/command.scm | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/module/system/repl/command.scm b/module/system/repl/command.scm index 0024fd165..4c4a667f3 100644 --- a/module/system/repl/command.scm +++ b/module/system/repl/command.scm @@ -61,7 +61,7 @@

bug#59321: ice-9's open-input-pipe is unexpectedly slow on some systems

p. There’s still the >> possibility that application bug unwillingly leaks FDs, but we could >> consider it’s none of our business. >> >> Thoughts? > > I agree with this approach in principle, but from what Tomas is saying > it seems like it's not currently possible

bug#59597: [PATCH 3/3] Change order of the resulting alist - a new entry is added to the start of the alist.

--- doc/ref/api-data.texi | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/ref/api-data.texi b/doc/ref/api-data.texi index 143434213..2f603fb8f 100644 --- a/doc/ref/api-data.texi +++ b/doc/ref/api-data.texi @@ -4785,11 +4785,11 @@ extract or change individual pieces of i

bug#59596: [PATCH 2/3] Add an interactive session exception error message.

--- doc/ref/api-data.texi | 5 + 1 file changed, 5 insertions(+) diff --git a/doc/ref/api-data.texi b/doc/ref/api-data.texi index 8c18b4d40..143434213 100644 --- a/doc/ref/api-data.texi +++ b/doc/ref/api-data.texi @@ -4798,6 +4798,11 @@ Notice that if we try the same @code{assq-set!} call wit

bug#59595: [PATCH 1/3] Add examples and incomplete wordings.

--- doc/ref/api-data.texi | 33 - 1 file changed, 32 insertions(+), 1 deletion(-) diff --git a/doc/ref/api-data.texi b/doc/ref/api-data.texi index 8658b9785..8c18b4d40 100644 --- a/doc/ref/api-data.texi +++ b/doc/ref/api-data.texi @@ -4767,7 +4767,7 @@ It also allo

bug#59572: [PATCH] Fix minor typo.

Hi, I'm new here.From efdb82fa7dc33c8b161a7783e11197c746a4959d Mon Sep 17 00:00:00 2001 From: Yuval Langer Date: Fri, 25 Nov 2022 13:04:28 +0200 Subject: [PATCH] Fix minor typo. --- doc/ref/api-data.texi | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/ref/api-data.tex

bug#59540: Calling length on a very long improper list is disastrous.

I lost my Emacs session today because I accidentally called the length function on an extremely long improper list. But Guile prints the entire thing when it reports the error that happens when the length function gets to the improper part of the list. It tried to print a few million elements just

bug#59321: ice-9's open-input-pipe is unexpectedly slow on some systems

rienced Guile > > hackers on the potential consequences of this change. > > Libguile opens all its own file descriptors at O_CLOEXEC (one omission > was recently fixed in 0aa1a9976fc3c6af4d1087e59d728cb8fe7d369a) so it > may be possible to remove that FD-closing loop. There’s still

bug#59321: ice-9's open-input-pipe is unexpectedly slow on some systems

le to remove that FD-closing loop. There’s still the > possibility that application bug unwillingly leaks FDs, but we could > consider it’s none of our business. > > Thoughts? Hm. Socket FDs don't "have" O_CLOEXEC. Arguably, they are at least as "interesting"

bug#59055: [PATCH] Fix possible deadlock.

On Sun, 20 Nov 2022, Ludovic Courtès wrote: > Did you try to come up with a reproducer? That would be awesome but I > guess it’s hard because you need to trigger EINTR at the right point. With a stress test in guile-parallel. Very hard to reproduce indeed. You can also reproduce it with `ice-9

bug#59021: Unbounded heap growth when combining dynamic states & delimited continuation

Hi, Ludovic Courtès skribis: > Ludovic Courtès skribis: > >> Consider this code: >> >> ;; https://issues.guix.gnu.org/58631 >> ;; https://github.com/wingo/fibers/issues/65 >> >> (define loss >> (make-vector 100)) >> >> (let ((tag (make-prompt-tag "my prompt"))) >> (define handler >>

bug#59321: ice-9's open-input-pipe is unexpectedly slow on some systems

sequences of this change. Libguile opens all its own file descriptors at O_CLOEXEC (one omission was recently fixed in 0aa1a9976fc3c6af4d1087e59d728cb8fe7d369a) so it may be possible to remove that FD-closing loop. There’s still the possibility that application bug unwillingly leaks FDs, but we could c

bug#59055: [PATCH] Fix possible deadlock.

Hi, Olivier Dion skribis: > If we got interrupted while waiting on our condition variable, we unlock > the kernel mutex momentarily while executing asynchronous operations > before putting us back into the waiting queue. > > However, we have to retry acquiring the mutex before getting back into

bug#59321: ice-9's open-input-pipe is unexpectedly slow on some systems

On Fri, Nov 18, 2022 at 02:49:05PM +1000, Andrew Whatson wrote: > Hi Nate, > > Thanks for reporting this! I'm able to reproduce on my systems, and > have identified the culprit: [250k calls to close()] Well spotted. Here [1] is a good discussion on the problem. Spoiler alert: there is no nice,

bug#59321: ice-9's open-input-pipe is unexpectedly slow on some systems

Hi Nate, Thanks for reporting this! I'm able to reproduce on my systems, and have identified the culprit: > strace -c -f guile -c '(begin (use-modules (ice-9 popen) (ice-9 rdelim)) (display (read-delimited "" (open-input-pipe "ls"' % time seconds usecs/call callserrors syscal

bug#57507: Regular expression matching depends on locale encoding

Le 05/09/2022 à 21:24, Ludovic Courtès a écrit : Yes, that’d be welcome. I would not call it a constraint or limitation; for example, that ‘w’ is not a letter in Swedish is the kind of thing you’d generally want to take into account. Now, it’d be nice if one could easily specify the locale to o

bug#59325: The documentation of `map` is confusing

The sentence '-- Scheme Procedure: map' is defined twice each with different inputs and explanation: -- Scheme Procedure: map proc arg1 arg2 ... -- Scheme Procedure: map-in-order proc arg1 arg2 ... -- C Function: scm_map (proc, arg1, args) Apply PROC to each element of the list ARG1 (if only two

bug#59321: ice-9's open-input-pipe is unexpectedly slow on some systems

Hi, while doing my first steps in Guile and porting a small shell script, I noticed that capturing stdout from a subshell is very slow: $ time guile -c '(begin (use-modules (ice-9 popen) (ice-9 rdelim)) (display (read-delimited "" (open-input-pipe "ls"' # real0m0,313s user0m0,008

bug#59221: (file-exists? #f) raises an exception

le-exists? #f) should return #f. > > > Why? > hmmm, somehow I missed your response. I guess for my simple use case, it just made more sense. I am defining a service for guix that asks for user input. If the user doesn't type in input, the default value was #f. That's fine.

bug#59221: (file-exists? #f) raises an exception

Le 13/11/2022 à 07:44, to...@tuxteam.de a écrit : You both have a point. Checking for existing predicates with a longer tradition, though: scheme@(guile-user)> (exact? "mumble") ice-9/boot-9.scm:1685:16: In procedure raise-exception: In procedure exact?: Wrong type argument in position

bug#59221: (file-exists? #f) raises an exception

On Sun, Nov 13, 2022 at 02:15:43AM +, jbranso--- via Bug reports for GUILE, GNU's Ubiquitous Extension Language wrote: > November 12, 2022 12:58 PM, "Jean Abou Samra" wrote: > > >> Le 12 nov. 2022 à 18:50, Joshua Branson via Bug reports for GUILE, GN

bug#59221: (file-exists? #f) raises an exception

November 12, 2022 12:58 PM, "Jean Abou Samra" wrote: >> Le 12 nov. 2022 à 18:50, Joshua Branson via Bug reports for GUILE, GNU's >> Ubiquitous Extension >> Language a écrit : >> >> Hello you lovely guile people! >> >> This bug is so si

bug#59221: (file-exists? #f) raises an exception

> Le 12 nov. 2022 à 18:50, Joshua Branson via Bug reports for GUILE, GNU's > Ubiquitous Extension Language a écrit : > >  > Hello you lovely guile people! > > This bug is so simple the subject line says it all! > > file-exists? is a predicate, but >

bug#59221: (file-exists? #f) raises an exception

Hello you lovely guile people! This bug is so simple the subject line says it all! file-exists? is a predicate, but #+BEGIN_SRC scheme (file-exists? #f) ice-9/boot-9.scm:1685:16: In procedure raise-exception: In procedure stat: Wrong type argument in position 1 (expecting open file port): #f

bug#57440: [patch] Guile manual has incorrect history on the name

> --- a/doc/ref/history.texi > +++ b/doc/ref/history.texi > @@ -69,7 +69,7 @@ the argument was that eventually when GEL became more > capable, it > could gain the ability to execute other languages, especially Emacs > Lisp. > > -Due to a naming conflict with another programming language, Jim B

bug#59204: Duplicate of bug#57440 — sorry for that, I still had it in my patch list and saw that it did not get killed on pull+rebase so I thought I had forgotten to send it.

close 59204 -- Unpolitisch sein heißt politisch sein, ohne es zu merken. draketo.de signature.asc Description: PGP signature

bug#59204: [PATCH] small history doc change: the name change was suggested by Lee Thomas

Hi, since I collected references from various newsgroups, I’d like to suggest this change to the history part of the docs: the name change to Guile was suggested by Lee Thomas. From e00afe1654773ac4e5eebe2e3ec4f0186c23d1f9 Mon Sep 17 00:00:00 2001 From: Arne Babenhauserheide Date: Sat, 27 Aug 20

bug#59203: [PATCH] add function string-split-substring

Hi, this patch adds the function string-split-substring. The existing string-split functions all only allow splitting by char or char_set, but common file formats like graphviz need to be split by strings like " -> ". Example usage: (string-split-substring line "key -> value" " -> ") ;; => '("ke

bug#56413: [PATCH 1/1] scm_i_utf8_string_hash: compute u8 chars not bytes

Hi, Rob Browning skribis: > Oh, and unless I'm missing something, I remembered why we may need to > keep the standalone C test program -- there's no straightforward way to > call scm_from_utf8_symbol() from scheme? Ah yes, you’re probably right! Ludo’.

bug#56413: [PATCH 1/1] scm_i_utf8_string_hash: compute u8 chars not bytes

Rob Browning writes: > OK, so unfortunately I don't actually recall how I came up with that > number, but I can start over with some canonical approach to compute the > value if we like. I hacked up hash.c to let me call wide_string_hash() directly and printed the hash for wchar_t {0x3A0, 0x3B5,

bug#59021: Unbounded heap growth when combining dynamic states & delimited continuation

Hi, Maxim Cournoyer writes: [...] > I've tested both 3.0.8 from Guix on multiple machines (including Berlin) > and 2.2 from Debian 10, and ran the above snippet; it grows initially > but stabilize quickly and then doesn't budge. I've let it run for more > than an hour. Actually, it does grow,

bug#59021: Unbounded heap growth when combining dynamic states & delimited continuation

Hi Ludovic, Ludovic Courtès writes: > (This is a followup to , > itself a followup to .) > > Consider this code: > > ;; https://issues.guix.gnu.org/58631 > ;; https://github.com/wingo/fibers/issues/65 > > (define loss

bug#56413: [PATCH 1/1] scm_i_utf8_string_hash: compute u8 chars not bytes

Rob Browning skribis: > So this change *could* alter results, but only for non-ASCII strings, > and those results would have been wrong (i.e. relying on uninitialized > memory). OK, that was my understanding too. > That leaves the size_t -> long change in scm_i_str2symbol(), and I don't > think

bug#56413: [PATCH 1/1] scm_i_utf8_string_hash: compute u8 chars not bytes

Rob Browning skribis: >> Is this a documented example of Jenkins? Or did you use a reference >> implementation? > > Jenkins? That’s the name of the hash function in question. If not, where did you get that example from? :-) Thanks, Ludo’.

bug#56413: [PATCH 1/1] scm_i_utf8_string_hash: compute u8 chars not bytes

Ludovic Courtès writes: > Rob Browning skribis: >> + // Make sure a utf-8 symbol has the expected hash. In addition to >> + // catching algorithmic regressions, this would have caught a >> + // long-standing buffer overflow. >> + >> + // περί >> + char about_u8[] = {0xce, 0xa0, 0xce, 0xb5

bug#56413: [PATCH 1/1] scm_i_utf8_string_hash: compute u8 chars not bytes

Rob Browning writes: > Jenkins? Oh, right (after looking back at the code). I'll get back to you regarding this and the other questions after I finish reviewing/remembering. Thanks -- Rob Browning rlb @defaultvalue.org and @debian.org GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39

bug#56413: [PATCH 1/1] scm_i_utf8_string_hash: compute u8 chars not bytes

Ludovic Courtès writes: > For the final patch please add a ChangeLog-style entry. Will do. > Is this a documented example of Jenkins? Or did you use a reference > implementation? Jenkins? > Yes, it may be nicer to have it in ‘test-suite/tests/hash.test’. > > AFAICS this will only change the

bug#56413: [PATCH 1/1] scm_i_utf8_string_hash: compute u8 chars not bytes

Hi, Rob Browning skribis: > Noticed while investigating a migration to utf-8 strings. After making > changes that routed non-ascii symbol hashing through this function, > encoding-iso88597.test began intermittently failing because it would > traverse trailing garbage when u8_strnlen reported 8

bug#59021: Unbounded heap growth when combining dynamic states & delimited continuation

Ludovic Courtès skribis: > Consider this code: > > ;; https://issues.guix.gnu.org/58631 > ;; https://github.com/wingo/fibers/issues/65 > > (define loss > (make-vector 100)) > > (let ((tag (make-prompt-tag "my prompt"))) > (define handler > (lambda (k i) > (when (zero? (modulo i

bug#59055: [PATCH] Fix possible deadlock.

If we got interrupted while waiting on our condition variable, we unlock the kernel mutex momentarily while executing asynchronous operations before putting us back into the waiting queue. However, we have to retry acquiring the mutex before getting back into the queue, otherwise it's possible tha

bug#59021: Unbounded heap growth when combining dynamic states & delimited continuation

(This is a followup to , itself a followup to .) Consider this code: --8<---cut here---start->8--- ;; https://issues.guix.gnu.org/58631 ;; https://github.com/wingo/fibers/issues/65 (

bug#58905: Vector initialization loop remains even when allocation is elided

Spot the issue in the code below? --8<---cut here---start->8--- scheme@(guile-user)> (version) $28 = "3.0.8" scheme@(guile-user)> ,c (let () (make-vector 12345 #\x) 42) Disassembly of at #xe8: 0(instrument-entry 42) at (u

bug#58524: Acknowledgement (pointer->procedure doesn't support foreign function use varargs.)

Any one interested in it? -- Retrieve my PGP public key: gpg --recv-keys B3EBC086AB0EBC0F45E0B4D433DB374BCEE4D9DC Zihao signature.asc Description: PGP signature

bug#58646: [PATCH] doc: Fix eval-when example

From 0e35d0494b7c6f05819e3386d404776a64a2e5c9 Mon Sep 17 00:00:00 2001 From: Jean Abou Samra Date: Wed, 19 Oct 2022 23:01:06 +0200 Subject: [PATCH] doc: Fix eval-when example * doc/ref/api-macros.texi: make the macro expand to the literal   date, not to a call to the date function.  The example

bug#55356: [PATCH] Always release thread data mutex in join-thread.

From: Olivier Dion Currently the mutex is only unlocked when results are available. However, it is not unlocked when we get a timeout from the condition variable. * module/ice-9/threads.scm (join-thread): Use with-mutex to ensure that the thread data mutex is always unlocked. --- module/ice-9/t

bug#58529: possible doc bug in guile manual

Sorry about the fat finger automagic send from gmail... Reading through the gnu manual, I wanted to get a better handle on some of @ module syntax introduced in: https://www.gnu.org/software/guile/manual/html_node/Scripting-Examples.html I cut and pasted fact and choose into their own files. I us

bug#58529: possible doc bug in guile manual

Hi, Reading through the gnu manual, I wanted to get a better handle on some of @ module syntax introduced in: https://www.gnu.org/software/guile/manual/html_node/Scripting-Examples.html I cut and pasted fact and choose into their own files. I used this version of choose:

bug#58524: pointer->procedure doesn't support foreign function use varargs.

In current implementation of pointer->procedure, it use ffi_prep_cif. So pointer->procedure just support foreign function with fixed amount of arguments. It's possible to support foreign function use varargs by using ffi_prep_cif_var. -- Retrieve my PGP public key: gpg --recv-keys B3EBC086AB

bug#58517: Bug: Module for SXPath not Documented

The module that provides the interface to SXPath was not clearly documented in the manual. I have provided a patch that does that to help future readers. Muriithi Frederick Muriuki https://fredmanglis.me.ke PGP Key Fingerprint: F370 F409 854B 90E3 52F3  AB01 362B 0BB8 B81D 5A42From b77236cebea0

bug#58498: Foreign callback returned by procedure->pointer cannot be executed in foreign thread.

The foreign function pointer returned by "procedure->pointer" can only executed in a thread which Scheme context is already initialized. This may not so convenient because foreign library may create its own thread and run our callback in foreign thread. To show what will happen, this is a small e

bug#57948: [PATCH] Avoid 'frame-local-ref' errors when printing backtrace.

Hi, Andrew Whatson skribis: > Ludovic Courtès wrote: >> >> It would be great if you could add a simple test case though, so that >> the bug doesn’t eventually come back to haunt us. >> >> Could you send an updated patch? > > Ah yes, getting this covered

bug#57948: [PATCH] Avoid 'frame-local-ref' errors when printing backtrace.

Ludovic Courtès wrote: > > It would be great if you could add a simple test case though, so that > the bug doesn’t eventually come back to haunt us. > > Could you send an updated patch? Ah yes, getting this covered in a test is on my list. I had trouble writing a reproducer prev

bug#58109: simple-format vs (ice-9 format) bug in 3.0.7?

Hi, Jean Abou Samra skribis: > OK, understood. How about adding comments and documentation? That’s a good idea. Applied with minor tweaks and a commit log. Thanks! Ludo’.

bug#57948: [PATCH] Avoid 'frame-local-ref' errors when printing backtrace.

most)! It would be great if you could add a simple test case though, so that the bug doesn’t eventually come back to haunt us. Could you send an updated patch? Thanks, Ludo’. PS: BTW, it’ll be great to have more patches from you! :-) To that end, please check out the new Guile copyright

bug#58297: GOOPS slot accessor specialization and inheritance do not compose

the type dispatch is done. (There were originally plans to actually also eliminate a lot of the type dispatch in GOOPS.) It should be possible to get the CLOS behavior by defining a suitable meta class. If *that* is not possible, it might be a bug, or at least a target for a feature request. Best

bug#58297: GOOPS slot accessor specialization and inheritance do not compose

e "Alice")) (defvar p2 (make-instance 'child :name "Bob")) ;; Both of these setf calls use the specialized setf method defined ;; above. (setf (name p1) "Ada") (setf (name p2) "Ben") I find the Common Lisp behavior much more desirable. Is this a bug or intended behavior? Thanks for reading, - Dave

bug#58109: simple-format vs (ice-9 format) bug in 3.0.7?

Le 01/10/2022 à 15:40, Ludovic Courtès a écrit : Hi, Jean Abou Samra skribis: Uh, at the end of module/ice-9/format.scm, there is ;; Thanks to Shuji Narazaki (module-set! the-root-module 'format format) which dates back to commit 14469b7c69feb0f2c5b8a093f19fe2a548b31c5b Author: Greg J.

bug#58217: tree-il->bytecode compilation of (not (list …)) fails

Ludovic Courtès skribis: > I believe this is fixed by changing ‘predicate?’ to: > > (define (predicate? name) > (and=> (lookup-primitive name) primitive-predicate?)) Done in e2797f529b8934b0a11b9f6aebbf937b183ece77! Ludo’.

bug#57377: [PATCH] api-coverage.texi: fix example, remove mentions of unimplemented features

Hi Antoine, Antoine Kalmbach skribis: > * doc/ref/api-coverage.texi (Code Coverage): #:modules is not > supported... never seems to have been supported? > (example): close port, not file. In commit 4456245753ff925cafd3e72d130761b6f1c2c419, Jessica Talon added support for #:modules. I appli

bug#57440: Guile manual has incorrect history on the name

Hi Arne and Lee, "Dr. Arne Babenhauserheide" skribis: > From 8bfc607ffbc433b7dde50787cf813bd455726daa Mon Sep 17 00:00:00 2001 > From: Arne Babenhauserheide > Date: Sat, 27 Aug 2022 01:57:57 +0200 > Subject: [PATCH] doc: Lee Thomas suggested the name change. Thanks for the historical research

bug#57776: [PATCH] * doc/ref/compiler.texi (CPS Soup) : fix small typo in doc (closing paren out of @code{} tag).

Applied, thanks!

bug#57778: [PATCH] * doc/ref/sxml.texi (7.21.4 Transforming SXML): adds a mention to the module to be imported for the procedures introduced in this section of the documentation.

Hi, Fulbert skribis: > Small change proposal in attached patch to give some direction on module > to use for functions discussed in the (7.21.4 Transforming SXML) section > of the documentation. A welcome improvement! > +The pre-post-order function, in (sxml transform) module, visits the

bug#58109: simple-format vs (ice-9 format) bug in 3.0.7?

Hi, Jean Abou Samra skribis: > Uh, at the end of module/ice-9/format.scm, there is > > ;; Thanks to Shuji Narazaki > (module-set! the-root-module 'format format) > > which dates back to > > commit 14469b7c69feb0f2c5b8a093f19fe2a548b31c5b > Author: Greg J. Badros > Date:   Thu Jan 20 20:58:30 20

bug#49941: [PATCH] module/system/base/target.scm: support riscv32

Hi, Fabrice Fontaine skribis: > Fix the following build failure on riscv32: > > system/base/target.scm:132:16: In procedure triplet-pointer-size: > unknown CPU word size "riscv32" > > Fixes: > - > http://autobuild.buildroot.org/results/6705630c1484239ec8b73d57ebc2e2570fbfc8f8 > > Signed-off-by

bug#58217: tree-il->bytecode compilation of (not (list …)) fails

Hi, I stumbled upon this bug of the baseline compiler: --8<---cut here---start->8--- scheme@(guile-user)> (compile '(not (list 1 2)) #:optimization-level 2) $3 = #f scheme@(guile-user)> (compile '(not (list 1 2)) #:optimization-level 1)

bug#58154: fluid-ref* with negative index segfaults

Fixed in c0004442b7691f59a0e37869ef288eb26382ad9e. Thank you!

bug#58154: fluid-ref* with negative index segfaults

antipode@antipode ~$ guile -c '(fluid-ref* (make-fluid) -1)' Backtrace: In ice-9/boot-9.scm: 1752:10 6 (with-exception-handler _ _ #:unwind? _ # _) In unknown file: 5 (apply-smob/0 #) In ice-9/boot-9.scm: 724:2 4 (call-with-prompt ("prompt") # …) In ice-9/eval.scm: 619:8 3

bug#58109: simple-format vs (ice-9 format) bug in 3.0.7?

licate of https://debbugs.gnu.org/cgi/bugreport.cgi?bug=50059 Uh, at the end of module/ice-9/format.scm, there is ;; Thanks to Shuji Narazaki (module-set! the-root-module 'format format) which dates back to commit 14469b7c69feb0f2c5b8a093f19fe2a548b31c5b Author: Greg J. Badros Date:   Thu Jan 20

bug#58109: simple-format vs (ice-9 format) bug in 3.0.7?

Le 27/09/2022 à 12:23, Christopher Lam a écrit : Hi guilers, here's a short bash session. Why would the first bash call to "guile s.scm" work, but not the second one? guile-3.0.7 on ubuntu. This is a duplicate of https://debbugs.gnu.org/cgi/bugreport.cgi?bug=50059

bug#58109: simple-format vs (ice-9 format) bug in 3.0.7?

Hi guilers, here's a short bash session. Why would the first bash call to "guile s.scm" work, but not the second one? guile-3.0.7 on ubuntu. $ cat s.scm (format #t "~f\n" 2.5) $ guile s.scm ;;; note: auto-compilation is enabled, set GUILE_AUTO_COMPILE=0 ;;; or p

bug#58066: pretty-print will make data modified by set-cdr! to random value

Le 24/09/2022 à 12:01, slbtty a écrit : GNU Guile 3.0.8 Using `guile3 < file.scm` to run the code below will makes the result of tp unpredictable (pointing to very random things) (use-modules (ice-9 pretty-print)) (define tl '(1 2)) (define tp (cdr tl)) (set-cdr! tp (cons 3 '())) (pretty-pri

bug#58068: pretty-print corrupts data modified by set-cdr!

GNU Guile 3.0.8 Using `guile3 < file.scm` to run the code below will makes the result of tp unpredictable (pointing to very random things) I am not sure about the set-cdr! and quote usage. However, i runned the same code in other schemes, mit, chicken, racket/r6rs, gambit, and they all yield tl a

bug#58066: pretty-print will make data modified by set-cdr! to random value

GNU Guile 3.0.8 Using `guile3 < file.scm` to run the code below will makes the result of tp unpredictable (pointing to very random things) (use-modules (ice-9 pretty-print)) (define tl '(1 2)) (define tp (cdr tl)) (set-cdr! tp (cons 3 '())) (pretty-print tl) (pretty-print tp) --- However, if

bug#55568: (no subject)

We discussed this again on IRC yesterday, see logs here: https://logs.guix.gnu.org/guile/2022-09-21.log#120814 We realised that the *real* underlying issue is that false-if-exception is not working in the context of my test code, i.e. when another exception handler is set up. See further info her

bug#58001: Cannot use 'read' in imported library

I'm using Guile version 3.0.5 from the Guix repository. I've run into a strange issue with the read function from (scheme base). It cannot be used in an R7RS-style library. This only seems to apply to the read function. Other standard procedures work fine. Let's say you have a library that us

bug#35430: close

Was fixed January 2021 in 1b0da42672262426bca7bb58e70fb753c628ffc3

bug#57948: Frame bindings referring to non-existent locals

I've submitted a workaround for this problem here: https://lists.gnu.org/archive/html/guile-devel/2022-09/msg00016.html

bug#57948: Frame bindings referring to non-existent locals

Hello Guilers! I have some buggy code which fails to compile. While printing the backtrace of this compilation error, another error occurs and Guile reports "Exception thrown while printing backtrace". To reproduce the error: $ git clone https://gitlab.com/flatwhatson/guile-prescheme.git $

bug#57808: [PATCH] string-fun: Fix typo

Applied in 9592516bfa23056542e9b05b00a4449d0809c6bc. Ty!

bug#57808: [PATCH] string-fun: Fix typo

--- module/ice-9/string-fun.scm | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/module/ice-9/string-fun.scm b/module/ice-9/string-fun.scm index 03e0238fa..592b49e20 100644 --- a/module/ice-9/string-fun.scm +++ b/module/ice-9/string-fun.scm @@ -30,7 +30,7 @@ ;;; -;;; Va

bug#57778: [PATCH] * doc/ref/sxml.texi (7.21.4 Transforming SXML): adds a mention to the module to be imported for the procedures introduced in this section of the documentation.

Small change proposal in attached patch to give some direction on module to use for functions discussed in the (7.21.4 Transforming SXML) section of the documentation. --- doc/ref/sxml.texi | 16 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/doc/ref/sxml.texi b/do

bug#57776: [PATCH] * doc/ref/compiler.texi (CPS Soup) : fix small typo in doc (closing paren out of @code{} tag).

--- doc/ref/compiler.texi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/ref/compiler.texi b/doc/ref/compiler.texi index 27964e881..865a77607 100644 --- a/doc/ref/compiler.texi +++ b/doc/ref/compiler.texi @@ -1120,7 +1120,7 @@ especially in cases when we know that we can j

bug#57567: ‘primitive-load’ should open files with O_CLOEXEC

Ludovic Courtès skribis: > Currently ‘primitive-load’ opens files without O_CLOEXEC: > > port = scm_open_file_with_encoding (filename, > scm_from_latin1_string ("r"), > SCM_BOOL_T, /* guess_encoding */ >

bug#57507: Regular expression matching depends on locale encoding

Hi, Jean Abou Samra skribis: > Le 05/09/2022 à 09:48, Ludovic Courtès a écrit : >> Hi Jean, >> >> Jean Abou Samra skribis: >> >>> Regular expressions do funky things with Unicode if a non-Unicode-aware >>> locale is set. Yet, they're purely string operations, so I don't think >>> it's expected

bug#57507: Regular expression matching depends on locale encoding

Le 05/09/2022 à 09:48, Ludovic Courtès a écrit : Hi Jean, Jean Abou Samra skribis: Regular expressions do funky things with Unicode if a non-Unicode-aware locale is set. Yet, they're purely string operations, so I don't think it's expected that they depend on the locale encoding. This is the

bug#57507: Regular expression matching depends on locale encoding

Hi Jean, Jean Abou Samra skribis: > Regular expressions do funky things with Unicode if a non-Unicode-aware > locale is set. Yet, they're purely string operations, so I don't think > it's expected that they depend on the locale encoding. This is the expected behavior: first because (ice-9 regex

bug#52835: [PATCH v5 0/3] Move spawning procedures to posix_spawn.

Hi everyone, As was discussed on IRC, if we're going to rewrite a non-negligible part of posix.c, let's at least do it right and use posix_spawn to handle the process spawning side of things. This is quite complex to get right in general (highlighted by this very bug) and so people ha

bug#52835: [PATCH v5 3/3] Move popen and posix procedures to spawn*.

* libguile/posix.c (renumber_file_descriptor, start_child, scm_piped_process): Remove functions. (scm_port_to_fd_with_default): New helper function. (scm_system_star): Rewrite using scm_spawn_process. (scm_init_popen): Remove the definition of piped-process. (scm_init_posix): Now make popen availab

bug#52835: [PATCH v5 2/3] Add spawn*.

* libguile/posix.c: Include spawn.h from Gnulib. (scm_spawn_process): New function. (scm_init_popen): Define spawn*. --- libguile/posix.c | 71 1 file changed, 71 insertions(+) diff --git a/libguile/posix.c b/libguile/posix.c index f4ca72d3e..5d287

<    1   2   3   4   5   6   7   8   9   10   >