bug#41938: Contradictory Information about Encoding in the Reference Manual
Section 4.3.1 (The Top of a Script File) of The Guile Reference Manual generated from the current master branch (3.0.2.152-1ab210) says: If this source code file is not ASCII or ISO-8859-1 encoded, a coding declaration such as ‘coding: utf-8’ should appear in a comment somewhere in the first five lines of the file: see *note Character Encoding of Source Files::. But section 6.18.8 (Character Encoding of Source Files) says: In the absence of any hints, UTF-8 is assumed. Probably the former information (ASCII or ISO-8859-1) is outdated.
bug#40737: Segfault in arm gcc7, thumb2 builroot, with arm patch
From: "Ludovic Courtès" > dsm...@roadrunner.com skribis: > > In the test-suite/standalone dir: > > while GUILE_JIT_THRESHOLD=0 make TESTS=test-language check-TESTS; > > OK. > > On IRC you mentioned that this does not happen with GUILE_JIT_THRESHOLD=-1, right? > That is correct. -Dale
bug#40582: Valid URIs are rejected
Hi, Julien Lepiller skribis: > Le 17 juin 2020 17:57:33 GMT-04:00, "Ludovic Courtès" a écrit : [...] >>The regexp below is still an approximation, but I think a better one. >>Can you confirm? >> >>Thanks, >>Ludo’. > > Looks slightly better, thanks. > > That's still incorrect, as it will match things that are not ipv6 addresses. > Does it have to be a regexp though? Why not simply check (false-if-exception > (inet-pton AF_INET6 host)), as in the return value of valid-host? Using a regexp makes the code closer to the RFC since the RFC explicitly describes the grammar. It’s also the simple choice here. > There's also a ipv6-host-pat that has an incorrect regexp, but I'm not sure > what it is used for. It’s use for ‘authority-regexp’, but that one is fine: it requires square brackets around IPv6 addresses. Pushed as 1ab2105339f60dba20c8c9680e49110501f3a6a0. Thanks, Ludo’.
bug#40737: Segfault in arm gcc7, thumb2 builroot, with arm patch
Hi, dsm...@roadrunner.com skribis: > I'm still seeing segfaults on rasbian on an rpi3. Have not tried > buildroot yet. > > That patch *did* fix a boatload of errors on arm, but this segfault is > an unrelated problem I think. Only happens on arm though. > > Here is a way to reproduce: > > In the test-suite/standalone dir: > while GUILE_JIT_THRESHOLD=0 make TESTS=test-language check-TESTS; do > :;done > > And then: > ../../meta/uninstalled-env ../../libtool --mode=execute gdb > ../../libguile/guile core > > Program terminated with signal SIGSEGV, Segmentation fault. > #0 0x76f505cc in scm_is_string (x=0x0) at strings.h:293 > 293 return SCM_HAS_TYP7 (x, scm_tc7_string); > [Current thread is 1 (Thread 0x76fe6010 (LWP 21616))] > (gdb) bt > #0 0x76f505cc in scm_is_string (x=0x0) at strings.h:293 > #1 scm_string_to_symbol (string=0x0) at symbols.c:361 > #2 0x722df4cc in ?? () > Backtrace stopped: previous frame identical to this frame (corrupt > stack?) OK. On IRC you mentioned that this does not happen with GUILE_JIT_THRESHOLD=-1, right? Thanks, Ludo’.
bug#40737: Segfault in arm gcc7, thumb2 builroot, with arm patch
I'm still seeing segfaults on rasbian on an rpi3. Have not tried buildroot yet. That patch *did* fix a boatload of errors on arm, but this segfault is an unrelated problem I think. Only happens on arm though. Here is a way to reproduce: In the test-suite/standalone dir: while GUILE_JIT_THRESHOLD=0 make TESTS=test-language check-TESTS; do :;done And then: ../../meta/uninstalled-env ../../libtool --mode=execute gdb ../../libguile/guile core Program terminated with signal SIGSEGV, Segmentation fault. #0 0x76f505cc in scm_is_string (x=0x0) at strings.h:293 293 return SCM_HAS_TYP7 (x, scm_tc7_string); [Current thread is 1 (Thread 0x76fe6010 (LWP 21616))] (gdb) bt #0 0x76f505cc in scm_is_string (x=0x0) at strings.h:293 #1 scm_string_to_symbol (string=0x0) at symbols.c:361 #2 0x722df4cc in ?? () Backtrace stopped: previous frame identical to this frame (corrupt stack?) -From: "Ludovic Courtès" To: dsm...@roadrunner.com Cc: 40...@debbugs.gnu.org Sent: Wednesday June 17 2020 6:36:34PM Subject: Re: bug#40737: Segfault in arm gcc7, thumb2 builroot, with arm patch Hi Dale, dsm...@roadrunner.com skribis: > Here is a backtrace of running guile on a builtroot constructed system > for rpi3. > Thumb2 instructions: BR2_ARM_INSTRUCTIONS_THUMB2=y > Gcc 7.5: BR2_GCC_VERSION="7.5.0" > Glibc. > > Uses the patch from >
bug#41929: backtrace when building os on a foreign distro
$ cat guix-os.scm (use-modules (gnu bootloader) (gnu bootloader grub) (gnu system file-systems)) (operating-system (host-name "jsynacek-guix-os") (timezone "Europe/Prague") (locale "en_US.utf8") (bootloader (bootloader-configuration (bootloader grub-efi-bootloader) (target "/dev/sdx"))) (file-systems (list (file-system (mount-point "/home") (device "/dev/sda33") (type "ext4") $ guix system build guix-os.scm Backtrace: In ice-9/boot-9.scm: 1736:10 4 (with-exception-handler _ _ #:unwind? _ #:unwind-for-type _) In unknown file: 3 (apply-smob/0 #) In ice-9/boot-9.scm: 718:2 2 (call-with-prompt _ _ #) In ice-9/eval.scm: 619:8 1 (_ #(#(#))) In guix/ui.scm: 1936:12 0 (run-guix-command _ . _) guix/ui.scm:1936:12: In procedure run-guix-command: In procedure struct-vtable: Wrong type argument in position 1 (expecting struct): #f Note that 'guix system init ...' and maybe other commands don't work too. 'guix system vm' with the above config file works without a backtrace. This is on guix 1.1.0 running on Fedora 32. I also tried to 'guix pull' but the result is the same. -- Jan Synacek Software Engineer, Red Hat
bug#37537: [PATCH] doc: Fix order of arguments to seek.
Hi, Arun Isaac skribis: > * doc/ref/r6rs.texi (rnrs io ports): Fix order of arguments to seek in > port-position and set-port-position! documentation. This was done as 59febb4b2d30211ad1dda161eedc3d72df8bff3d. Closing. Ludo’.
