unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: ludovic.courtes@laas.fr (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: [PATCH] Test-suite update
Date: Fri, 23 Sep 2005 11:54:31 +0200	[thread overview]
Message-ID: <87vf0sjei0.fsf@laas.fr> (raw)
In-Reply-To: <87oe6kyjnk.fsf@ossau.uklinux.net> (Neil Jerram's message of "Thu, 22 Sep 2005 20:41:51 +0100")

Hi,

Neil Jerram <neil@ossau.uklinux.net> writes:

> Actually I'm not sure I understand.  Do you see the stack overflow
> only after applying your patch, or did it occur before the patch also
> on your system?  I don't see a problem on Intel using current CVS.

When running `elisp.test' untouched.  Here's what I get:

  $ guile -L .. -l tests/elisp.test
  [...]
  PASS: scheme: value preservation: cdr
  PASS: scheme: value preservation: vector-ref
  ERROR: Stack overflow

Adding `format' expressions shows that this seems to occur when evaluating:

  (if (defined? '%nil)
      (use-modules (lang elisp interface)))

However, it works when run like this:

  $ guile -L ..
  guile> (load "tests/elisp.test")
  PASS: scheme: nil value is a boolean: boolean?
  [...]
  PASS: elisp: (defvar x 4)
  PASS: elisp: x
  guile>

So I tried the following:

  $ guile -L ..  -c '(begin (set! %load-hook (lambda (f) (format #t "loading ~a...~%" f))) (load "tests/elisp.test"))'
  loading tests/elisp.test...
  [...]
  PASS: scheme: value preservation: vector-ref
  loading ../lang/elisp/interface.scm...
  [...]
  PASS: elisp: (defvar x 4)
  PASS: elisp: x

And here everything works fine.

Any idea of the difference between `-l' and `load'?  Looking at
`script.c', that seems equivalent.

Thanks,
Ludovic.


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel


  reply	other threads:[~2005-09-23  9:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87oecutxox.fsf@laas.fr>
     [not found] ` <87vf58cxxq.fsf@zagadka.de>
     [not found]   ` <87k6kwopv5.fsf@laas.fr>
     [not found]     ` <87fysk7ady.fsf@zagadka.de>
     [not found]       ` <87mzmpmcm2.fsf@laas.fr>
     [not found]         ` <87aci6u6f4.fsf@laas.fr>
     [not found]           ` <87psr22c2p.fsf@zip.com.au>
2005-09-22 13:57             ` [PATCH] Test-suite update Ludovic Courtès
2005-09-22 19:25               ` Neil Jerram
2005-09-22 19:41                 ` Neil Jerram
2005-09-23  9:54                   ` Ludovic Courtès [this message]
2005-09-23 18:57                     ` Neil Jerram
2005-09-26  8:49                       ` Ludovic Courtès
2005-09-26 23:15                         ` Kevin Ryde
2005-09-22 21:15               ` Kevin Ryde
2005-09-22 22:06                 ` Kevin Ryde
2005-09-23  7:43                 ` Ludovic Courtès
2005-09-23 23:54                   ` Kevin Ryde
2005-09-26  8:35                     ` Ludovic Courtès
2005-09-26 23:18                       ` Kevin Ryde
     [not found]             ` <87irwtqkop.fsf@laas.fr>
     [not found]               ` <87slvog9sd.fsf@zip.com.au>
     [not found]                 ` <87wtkt9xyq.fsf_-_@laas.fr>
     [not found]                   ` <87hdbg4dl7.fsf@laas.fr>
     [not found]                     ` <87br1nakge.fsf@zip.com.au>
     [not found]                       ` <87hdbfnu9n.fsf@laas.fr>
     [not found]                         ` <87d5m2twaf.fsf@uni-dortmund.de>
     [not found]                           ` <878xwjb123.fsf@laas.fr>
     [not found]                             ` <874q76h9rh.fsf@zip.com.au>
     [not found]                               ` <87hdb5qogp.fsf@zagadka.de>
     [not found]                                 ` <87zmovn4y5.fsf@zip.com.au>
     [not found]                                   ` <87fyqn1gzy.fsf@laas.fr>
     [not found]                                     ` <87br196yd8.fsf@zip.com.au>
2005-11-02 10:50                                       ` Socket API improvement, patch #6 Ludovic Courtès
2005-11-02 20:07                                         ` Kevin Ryde
2005-11-03  9:00                                           ` Ludovic Courtès

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87vf0sjei0.fsf@laas.fr \
    --to=ludovic.courtes@laas.fr \
    --cc=guile-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).