Right now, in xterm 3, if I do:

(define x (make-thread ...some code to throw an error...))
(thread-start! x) ; a new xterm window pops up
(thread-terminate! x)

now, my new xterm window is useless, however it still sticks around -- is there a way to have that xterm window auto vanish on the thread being killed?

[I'm not quite seeing an ibvious way to do this.[

Thanks!

On Fri, Jun 19, 2009 at 10:10 AM, lowly coder <lowlycoder@huoyanjinjing.com> wrote:
Confirming that everything appears to wotk using git repo's latest Gambit.


On Thu, Jun 18, 2009 at 10:36 AM, Marc Feeley <feeley@iro.umontreal.ca> wrote:

On 17-Jun-09, at 6:29 PM, Marc Feeley wrote:

On 17-Jun-09, at 4:08 PM, lowly coder wrote:

~$ uname -a
Linux x 2.6.27-7-generic #1 SMP Fri Oct 24 06:40:41 UTC 2008 x86_64
GNU/Linux

~$ gsi -v
v4.4.2 20090315000833 x86_64-unknown-linux-gnu

(Ubuntu Linux)

I didn't make any changes ... I just followed the README file.

It seems that there is a problem with the procedure tcp-client-peer-
socket-info on Linux.  In the remote debugging code this is only used
for synchronization (to make sure the xterm has started before sending
it stuff to display).

Here's how to fix debugger.scm:

1) remove the call (tcp-client-peer-socket-info port)

2) before the first (let loop () ...  insert (thread-sleep! 2)

Marc

Indeed this problem only happens on Linux.  A patch which fixes this problem has been committed to the repository.  You should be able to run the original code on Linux now.

Marc