GNU logs - #46241, boring messages

Message sent to bug-guix@HIDDEN:

Subject: bug#46241: Guile Macros did not print the error-line-number ?
Resent-From: Joshua Branson <jbranso@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-guix@HIDDEN
Resent-Date: Mon, 01 Feb 2021 18:13:02 +0000
Resent-Message-ID: <handler.46241.B.161220317827694 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: 46241 <at> debbugs.gnu.org
Cc: bug-guile@HIDDEN
Date: Mon, 01 Feb 2021 13:12:42 -0500
Message-Id: <87r1lzodwl.fsf@HIDDEN>
From: Joshua Branson <jbranso@HIDDEN>
Received-SPF: pass client-ip=78.46.223.134; envelope-from=jbranso@HIDDEN;
 helo=mx1.dismail.de
X-Spam_score_int: -43
X-Spam_score: -4.4
X-Spam_bar: ----
X-Spam_report: (-4.4 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1,
 DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1,
 RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001,
 SPF_PASS=-0.001 autolearn=ham autolearn_force=no
X-Spam_action: no action
X-Spam-Score: -1.4 (-)
X-BeenThere: debbugs-submit <at> debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
X-Spam-Score: -2.4 (--)

Hello!

Recently on irc, I posted an example of an incorrectly used
define-record-type* NOT displaying an error line number.

mdevos mentioned that this could potentially be fixed in (guix
records), but it may also be a guile compile bug as well.

First here is a (guix records) example:

#+BEGIN_SRC scheme
(use-modules (guix records))

(define-record-type* <sway-bindsym>
  sway-bindsym make-sway-bindsym
  sway-bindsym?
  (key-combo sway-bindsym-key-combo
             (default "")))

(display sway-bindsym)  ;; compile error at unknown location
;; (display (sway-bindsym))  this is one "correct" way to call this code
#+END_SRC

One will get a compile error like the following

#+BEING_SRC sh 
;;; note: source file /home/joshua/prog/guile/test.scm
;;;       newer than compiled /home/joshua/.cache/guile/ccache/3.0-LE-8-4.4/home/joshua/prog/guile/test.scm.go
;;; note: auto-compilation is enabled, set GUILE_AUTO_COMPILE=0
;;;       or pass the --no-auto-compile argument to disable.
;;; compiling /home/joshua/prog/guile/test.scm
;;; WARNING: compilation of /home/joshua/prog/guile/test.scm failed:
;;; Syntax error:
;;; unknown location: source expression failed to match any pattern in form sway-bindsym
ice-9/psyntax.scm:2800:12: In procedure syntax-violation:
Syntax error:
unknown location: source expression failed to match any pattern in form sway-bindsym
#+END_SRC

As you can see, you do NOT see a error-line-number.  If this file was
sufficiently large, this might be hard to track down.  Though it IS
NICE to see that the error comes from an "sway-bindsym".

mdevos then mentioned that I should provide a simple use case NOT
involving (guix records).  Here is one:

#+BEGIN_SRC scheme
(define-syntax when
  (syntax-rules ()
    ((when condititon exp ...)
     (if condititon
         (begin exp ...)))))

(when #t (display "Hello\n"))

(display when)
#+END_SRC

The error message looks like:

#+BEGIN_SRC sh
;;; note: source file /home/joshua/prog/guile/macro-bug.scm
;;;       newer than compiled /home/joshua/.cache/guile/ccache/3.0-LE-8-4.4/home/joshua/prog/guile/macro-bug.scm.go
;;; note: auto-compilation is enabled, set GUILE_AUTO_COMPILE=0
;;;       or pass the --no-auto-compile argument to disable.
;;; compiling /home/joshua/prog/guile/macro-bug.scm
;;; WARNING: compilation of /home/joshua/prog/guile/macro-bug.scm failed:
;;; Syntax error:
;;; unknown location: source expression failed to match any pattern in form when
Hello
ice-9/psyntax.scm:2800:12: In procedure syntax-violation:
Syntax error:
unknown location: source expression failed to match any pattern in form when
#+END_SRC

Again, I do not see an error-line-number message.

Thanks,

Joshua

P.S. I am no scheme compiler expert.  As far as I know, maybe it's
impossible to display the error-line-number, when you use macros.  I
just heard that few free software users report bugs.  I'm just trying
to be helpful.  :)   I hope I am.

Message sent:

Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailer: MIME-tools 5.505 (Entity 5.505)
Content-Type: text/plain; charset=utf-8
X-Loop: help-debbugs@HIDDEN
From: help-debbugs@HIDDEN (GNU bug Tracking System)
To: Joshua Branson <jbranso@HIDDEN>
Subject: bug#46241: Acknowledgement (Guile Macros did not print the
 error-line-number ?)
Message-ID: <handler.46241.B.161220317827694.ack <at> debbugs.gnu.org>
References: <87r1lzodwl.fsf@HIDDEN>
X-Gnu-PR-Message: ack 46241
X-Gnu-PR-Package: guix
Reply-To: 46241 <at> debbugs.gnu.org
Date: Mon, 01 Feb 2021 18:13:02 +0000

Thank you for filing a new bug report with debbugs.gnu.org.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
 bug-guix@HIDDEN

If you wish to submit further information on this problem, please
send it to 46241 <at> debbugs.gnu.org.

Please do not send mail to help-debbugs@HIDDEN unless you wish
to report a problem with the Bug-tracking system.

--=20
46241: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=3D46241
GNU Bug Tracking System
Contact help-debbugs@HIDDEN with problems

Message sent to bug-guix@HIDDEN:

Subject: bug#46241: Guile Macros did not print the error-line-number ?
Resent-From: Ludovic =?UTF-8?Q?Court=C3=A8s?= <ludo@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-guix@HIDDEN
Resent-Date: Fri, 19 Feb 2021 15:15:02 +0000
Resent-Message-ID: <handler.46241.B.161374765216217 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: 46241 <at> debbugs.gnu.org
Cc: bug-guile@HIDDEN, jbranso@HIDDEN
From: Ludovic =?UTF-8?Q?Court=C3=A8s?= <ludo@HIDDEN>
References: <87r1lzodwl.fsf@HIDDEN>
Date: Fri, 19 Feb 2021 16:14:07 +0100
In-Reply-To: <87r1lzodwl.fsf@HIDDEN> (jbranso's message of "Mon, 01 Feb
 2021 13:12:42 -0500")
Message-ID: <877dn4m6o0.fsf@HIDDEN>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Precedence: list
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>

Hi Joshua,

jbranso--- via Bug reports for GNU Guix <bug-guix@HIDDEN> skribis:

> Recently on irc, I posted an example of an incorrectly used
> define-record-type* NOT displaying an error line number.
>
> mdevos mentioned that this could potentially be fixed in (guix
> records), but it may also be a guile compile bug as well.
>
> First here is a (guix records) example:
>
> #+BEGIN_SRC scheme
> (use-modules (guix records))
>
> (define-record-type* <sway-bindsym>
>   sway-bindsym make-sway-bindsym
>   sway-bindsym?
>   (key-combo sway-bindsym-key-combo
>              (default "")))
>
> (display sway-bindsym)  ;; compile error at unknown location
> ;; (display (sway-bindsym))  this is one "correct" way to call this code
> #+END_SRC

Source location info is missing because currently (as of 3.0.5), Guile
keeps location info in the form of =E2=80=9Csource properties=E2=80=9D only=
 for lists.
The =E2=80=98sway-bindsym=E2=80=99 symbol above has no associated location =
info.

This may change in the near future as Andy has been rewriting =E2=80=98read=
=E2=80=99
(the Scheme =E2=80=9Cparser=E2=80=9D) in Scheme, among other things.

Ludo=E2=80=99.

Message sent to bug-guix@HIDDEN:

Subject: bug#46241: Guile Macros did not print the error-line-number ?
Resent-From: Ludovic =?UTF-8?Q?Court=C3=A8s?= <ludo@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-guix@HIDDEN
Resent-Date: Fri, 19 Feb 2021 15:15:02 +0000
Resent-Message-ID: <handler.46241.B46241.161374765816237 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: 46241 <at> debbugs.gnu.org
Cc: bug-guile@HIDDEN, jbranso@HIDDEN
From: Ludovic =?UTF-8?Q?Court=C3=A8s?= <ludo@HIDDEN>
References: <87r1lzodwl.fsf@HIDDEN>
Date: Fri, 19 Feb 2021 16:14:07 +0100
In-Reply-To: <87r1lzodwl.fsf@HIDDEN> (jbranso's message of "Mon, 01 Feb
 2021 13:12:42 -0500")
Message-ID: <877dn4m6o0.fsf@HIDDEN>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Precedence: list
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>

Hi Joshua,

jbranso--- via Bug reports for GNU Guix <bug-guix@HIDDEN> skribis:

> Recently on irc, I posted an example of an incorrectly used
> define-record-type* NOT displaying an error line number.
>
> mdevos mentioned that this could potentially be fixed in (guix
> records), but it may also be a guile compile bug as well.
>
> First here is a (guix records) example:
>
> #+BEGIN_SRC scheme
> (use-modules (guix records))
>
> (define-record-type* <sway-bindsym>
>   sway-bindsym make-sway-bindsym
>   sway-bindsym?
>   (key-combo sway-bindsym-key-combo
>              (default "")))
>
> (display sway-bindsym)  ;; compile error at unknown location
> ;; (display (sway-bindsym))  this is one "correct" way to call this code
> #+END_SRC

Source location info is missing because currently (as of 3.0.5), Guile
keeps location info in the form of =E2=80=9Csource properties=E2=80=9D only=
 for lists.
The =E2=80=98sway-bindsym=E2=80=99 symbol above has no associated location =
info.

This may change in the near future as Andy has been rewriting =E2=80=98read=
=E2=80=99
(the Scheme =E2=80=9Cparser=E2=80=9D) in Scheme, among other things.

Ludo=E2=80=99.

Last modified: Fri, 19 Feb 2021 15:30:02 UTC

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997 nCipher Corporation Ltd, 1994-97 Ian Jackson.