From: Neil Jerram <neil@ossau.uklinux.net>
To: "carlo.bramix" <carlo.bramix@libero.it>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: Again on Windows support (2)
Date: Wed, 17 Jun 2009 22:09:08 +0100 [thread overview]
Message-ID: <87ab46efez.fsf@arudy.ossau.uklinux.net> (raw)
In-Reply-To: <87eitiegpf.fsf@arudy.ossau.uklinux.net> (Neil Jerram's message of "Wed\, 17 Jun 2009 21\:41\:16 +0100")
Neil Jerram <neil@ossau.uklinux.net> writes:
> "carlo.bramix" <carlo.bramix@libero.it> writes:
>
>> $ ./pre-inst-guile -c '(display "foo")'
>> Backtrace:
>> In unknown file:
>> ?: 0* (begin (eval-string "(display") (quit))
>> ?: 1* [eval-string "(display"]
>
> That is weird.
>
> Can we first rule out a problem with your shell? What output do you
> get from this?
>
> $ set - '(display "foo")' && echo "--${1}--" && echo "--${2}--"
Assuming that that gives the expected output, i.e.
--(display "foo")--
----
my next suggestion would be to run under GDB, with a breakpoint on
scm_shell(). The invocation for doing that is
./pre-inst-guile-env ./libtool --mode=execute gdb libguile/guile -c '(display "foo")'
In scm_shell, I would expect:
argc to be 3
argv[1] to be "-c"
argv[2] to be "(display \"foo\")"
scm_get_meta_args () to return 0
and hence not to execute the "if (new_argv)" block of code.
Can you check those points?
Regards,
Neil
next prev parent reply other threads:[~2009-06-17 21:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-16 18:26 Again on Windows support (2) carlo.bramix
2009-06-17 20:41 ` Neil Jerram
2009-06-17 21:09 ` Neil Jerram [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-06-19 8:15 carlo.bramix
2009-06-19 17:50 ` Neil Jerram
2009-06-19 8:48 carlo.bramix
2009-06-19 17:58 ` Neil Jerram
2009-06-19 18:09 ` Neil Jerram
2009-06-19 14:17 carlo.bramix
2009-06-19 16:17 ` Ludovic Courtès
2009-06-19 18:30 ` Ludovic Courtès
2009-06-19 19:11 carlo.bramix
2009-06-20 10:53 ` Andy Wingo
2009-06-22 9:18 carlo.bramix
2009-06-22 10:22 carlo.bramix
2009-06-23 9:41 carlo.bramix
2009-06-26 18:45 carlo.bramix
2009-07-01 18:55 carlo.bramix
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=87ab46efez.fsf@arudy.ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=carlo.bramix@libero.it \
--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).