From: "carlo\.bramix" <carlo.bramix@libero.it>
To: "guile-devel" <guile-devel@gnu.org>
Subject: Re: Again on Windows support (2)
Date: Fri, 19 Jun 2009 10:48:23 +0200 [thread overview]
Message-ID: <KLH9SN$530BA166F2576E736153FF9B67F7C9BB@libero.it> (raw)
Hello,
this is the command that I gave me some results:
$ ./pre-inst-guile-env ./libtool --mode=execute gdb --args libguile/guile.exe -c '(display "foo")'
As you can see I added "--args" option to GDB.
Without "--args" option, GDB says:
C:\msys\1.0\home\Carlo\guile/(display "foo"): Invalid argument.
argc=1
argv[0]=C:/msys/1.0/home/Carlo/guile/libguile/.libs/guile.exe
With "--args" option I had this:
argc=4
argv[0]=C:/msys/1.0/home/Carlo/guile/libguile/.libs/guile.exe
argv[1]=-c
argv[2]=\(display\
argv[3]="foo"\)
Since I had no idea about those unknown '\' characters, I added some debug prints before scm_boot_guile():
int
main (int argc, char **argv)
{
int x;
printf("argc=%d\n",argc);
for (x=0; x<argc; x++)
printf("argv[%d]=%s\n",x,argv[x]);
scm_boot_guile (argc, argv, inner_main, 0);
return 0; /* never reached */
}
Then I launched libguile/guile.exe normally and I got this:
argc=4
argv[0]=C:/msys/1.0/home/Carlo/guile/libguile/.libs/guile.exe
argv[1]=-c
argv[2]=(display
argv[3]=foo)
In this case, no more '/' but the '"' characters around the "foo" word are disappeared.
Anyways, I seems that the parameter has been split in two...
Sincerely,
Carlo Bramini.
---------- Initial Header -----------
From : "Neil Jerram" neil@ossau.uklinux.net
To : "carlo.bramix" carlo.bramix@libero.it
Cc : "guile-devel" guile-devel@gnu.org
Date : Wed, 17 Jun 2009 22:09:08 +0100
Subject : Re: Again on Windows support (2)
> 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 reply other threads:[~2009-06-19 8:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-19 8:48 carlo.bramix [this message]
2009-06-19 17:58 ` Again on Windows support (2) Neil Jerram
2009-06-19 18:09 ` Neil Jerram
-- strict thread matches above, loose matches on Subject: below --
2009-07-01 18:55 carlo.bramix
2009-06-26 18:45 carlo.bramix
2009-06-23 9:41 carlo.bramix
2009-06-22 10:22 carlo.bramix
2009-06-22 9:18 carlo.bramix
2009-06-19 19:11 carlo.bramix
2009-06-20 10:53 ` Andy Wingo
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 8:15 carlo.bramix
2009-06-19 17:50 ` Neil Jerram
2009-06-16 18:26 carlo.bramix
2009-06-17 20:41 ` Neil Jerram
2009-06-17 21:09 ` Neil Jerram
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='KLH9SN$530BA166F2576E736153FF9B67F7C9BB@libero.it' \
--to=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).