unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: "carlo\.bramix" <carlo.bramix@libero.it>
To: "guile-devel" <guile-devel@gnu.org>
Subject: Again on Windows support (2)
Date: Tue, 16 Jun 2009 20:26:24 +0200	[thread overview]
Message-ID: <KLCGK0$E7DE1BA20245A272E542BA80AED96C34@libero.it> (raw)

Hello,
after a while I decided to take again guile and I tried to continue the test on mingw+msys.
In one of the messages posted in thread "Again on Windows support" it has been said to me to put in ~/.guile:

  (debug-enable 'backtrace)
  (debug-set! depth 80)

Since I was not able to do this test with .guile, I tried to modify directly the values in the sources.
Into libguile/eval.c I temporally changed the initialization of some scm_debug_opts[] as:

{ SCM_OPTION_INTEGER, "depth", 80, "Maximal length of printed backtrace." },
{ SCM_OPTION_BOOLEAN, "backtrace", 1, "Show backtrace on error." },
{ SCM_OPTION_BOOLEAN, "debug", 1, "Use the debugging evaluator." },

I hope I changed the right points.
After that, I recompiled and I got this result on console:

cat alist.doc arbiters.doc async.doc backtrace.doc boolean.doc chars.doc continuations.doc debug.doc deprecation.doc deprecated.doc discouraged.doc dynl.doc dynwind.doc eq.doc error.doc eval.doc evalext.doc extensions.doc feature.doc fluids.doc fports.doc futures.doc gc.doc goops.doc gsubr.doc gc-mark.doc gc-segment.doc gc-malloc.doc gc-card.doc gettext.doc gc-segment-table.doc guardians.doc hash.doc hashtab.doc hooks.doc i18n.doc init.doc ioext.doc keywords.doc lang.doc list.doc load.doc macros.doc mallocs.doc modules.doc numbers.doc objects.doc objprop.doc options.doc pairs.doc ports.doc print.doc procprop.doc procs.doc properties.doc random.doc rdelim.doc read.doc root.doc rw.doc scmsigs.doc script.doc simpos.doc smob.doc sort.doc srcprop.doc stackchk.doc stacks.doc stime.doc strings.doc srfi-4.doc srfi-13.doc srfi-14.doc strorder.doc strports.doc struct.doc symbols.doc threads.doc throw.doc values.doc variable.doc vectors.doc version.doc vports.doc weaks.doc ramap.doc unif.doc dynl.doc filesys.doc posix.doc net_db.doc socket.doc win32-uname.doc win32-dirent.doc win32-socket.doc regex-posix.doc inet_aton.doc mkstemp.doc | GUILE="/home/Carlo/guile/pre-inst-guile" ../../guile-svn/scripts/snarf-check-and-output-texi          > guile-procedures.texi || { rm guile-procedures.texi; false; }
Backtrace:
In unknown file:
   ?: 0* (begin # # #)
   ?: 1* [eval-string "(apply"]

<unnamed port>: In procedure scm_i_lreadparen in expression (eval-string "(apply"):
<unnamed port>: #<unknown port>:1:7: end of file
make[3]: *** [guile-procedures.texi] Error 1

I also did the tests suggested to me in the past (first test does not print anything):

$ ./pre-inst-guile -c 1

$ ./pre-inst-guile -c '(display "foo")'
Backtrace:
In unknown file:
   ?: 0* (begin (eval-string "(display") (quit))
   ?: 1* [eval-string "(display"]

<unnamed port>: In procedure scm_i_lreadparen in expression (eval-string "(display"):
<unnamed port>: #<unknown port>:1:9: end of file

I hope you may have an idea about what it is happening.

Sincerely,

Carlo Bramini.






             reply	other threads:[~2009-06-16 18:26 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-16 18:26 carlo.bramix [this message]
2009-06-17 20:41 ` Again on Windows support (2) Neil Jerram
2009-06-17 21:09   ` Neil Jerram
  -- 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='KLCGK0$E7DE1BA20245A272E542BA80AED96C34@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).