On Mon, Jan 18, 2010 at 12:51 PM, REPLeffect repleffect@gmail.com wrote:
On Mon, Jan 18, 2010 at 12:09 PM, REPLeffect repleffect@gmail.com wrote:
On Mon, Jan 18, 2010 at 12:00 PM, REPLeffect repleffect@gmail.com wrote:
On Mon, Jan 18, 2010 at 11:41 AM, James Long longster@gmail.com wrote:
On Mon, Jan 18, 2010 at 12:28 PM, REPLeffect repleffect@gmail.com wrote:
Yeah, this morning I found the REPL-OUTPUT-REDIRECT in the previous version of swank-gambit.scm and had set it to #f to get the error messages to the terminal. Just now I downloaded the lastest version and set it up with SWANK-DEBUG to #t, and I get the same error message as I did with the previous version of swank-gambit.scm (here I typed in the undefined symbol 'sdf'):
(emacs==> (:emacs-rex (swank:listener-eval "sdf ") "???" :repl-thread 3)) ------------- REPL is now in #<thread #2 #<input-output-port #3 (tcp-client)>> ------------- *** ERROR IN exception-message, "swank-gambit.scm"@340.14 -- Wrong number of arguments passed to procedure (call-with-output-string "" '#<procedure #4>)
Great. I don't know why that's erroring. I'm using Gambit v4.5.2, has that procedure changed? Can you try to evaluate something like this: (call-with-output-string "" (lambda (p) (display "sdfd" p))) See if it works? I don't have time to look into it right now, but it looks like it might be easy to fix if you want to have a crack at it.
- James
Wow, I hadn't tried running call-with-output-string separately, I'd just looked at the code that called it and didn't see anything wrong with it. However, when I ran your suggested code I got the exact same error. Then I tried it on the Mac Mini, and it printed out the results with no errors. I'm using the exact same source code of gambit on both machines, so the results surprise me a little. I'm going to try building that version of gambit on another Linux machine I have and see if the results are the same.
Interestingly enough, the rebuilt code on the other Linux machine has the exact same error message. I'm going to try downloading the latest version of Gambit and see if the problem goes away.
Nope. Gambit 4.6.0 gives the exact same error message under Linux. It was compiled using gcc 4.3.2 (from the current Debian 5.0 package). I ran configure only with the --enable-single-host option. I did run 'make check' before installing, and all of the tests passed.
I am now recompiling without the --enable-single-host option, to see if that makes any difference.
And nope, configuring without --enable-single-host made no difference (I wasn't really expecting it to, but I thought it was worth trying).
Sorry, I thought I had been sending all of this to the list and instead was just sending/replying to James' email. I have filled in the missing messages above.
Afficher les réponses par date
On 2010-01-18, at 2:07 PM, REPLeffect wrote:
And nope, configuring without --enable-single-host made no difference (I wasn't really expecting it to, but I thought it was worth trying).
Sorry, I thought I had been sending all of this to the list and instead was just sending/replying to James' email. I have filled in the missing messages above.
Please provide the following info:
- gsi -v - uname -a - a transcript of the error - a (pp #4)
and post it to the bugzilla bug report tracker.
Marc
On Mon, Jan 18, 2010 at 1:20 PM, Marc Feeley feeley@iro.umontreal.ca wrote:
On 2010-01-18, at 2:07 PM, REPLeffect wrote:
And nope, configuring without --enable-single-host made no difference (I wasn't really expecting it to, but I thought it was worth trying).
Sorry, I thought I had been sending all of this to the list and instead was just sending/replying to James' email. I have filled in the missing messages above.
Please provide the following info:
- gsi -v - uname -a - a transcript of the error - a (pp #4)
and post it to the bugzilla bug report tracker.
Marc
Will do. It will be there shortly.