Re: Thread + Socket + Pipes Bug?

[Neil Jerram]

Robert,

I'm having trouble reproducing the problem, and I also have some
questions about the code.

1. Repro

Can you be precise about "dumping data" to port 6008.  I've tried
running with just ./buggy.scm in one window, and the following in
another window...

address@hidden ~]$ telnet localhost 6008
Trying ::1...
telnet: connect to address ::1: Connection refused
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
bye
bye again
^]
telnet> close
Connection closed.
address@hidden ~]$ telnet localhost 6008
Trying ::1...
telnet: connect to address ::1: Connection refused
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
hello
hello again
hello 3
hello 4
^]
telnet> close
Connection closed.

...but I don't see any error (or any other output/result) anywhere.

2. Code

Why do you need to lock and unlock the mutex so much on the main
thread?  It looks to me as though the data protected by the mutex is
just `message' - is that correct?

Regards,
        Neil


>>>>> "Robert" == Robert Marlow <address@hidden> writes:

    Robert> Hi Neil
    Robert> Sorry, I think I neglected to mention. I'm using Guile 1.6.4 on 
Solaris
    Robert> and GNU/Linux.

    Robert> Thanks heaps for checking it out.


    Robert> On Fri, 2003-08-08 at 05:25, Neil Jerram wrote:
    >> Robert,
    >> 
    >> You probably said in your earlier reports, but ... which version(s) of
    >> Guile do you see this bug with?
    >> 
    >> (I'll try to make time over the weekend to investigate ...)
    >> 
    >> Thanks,
    >> Neil
    Robert> -- 
    Robert> Regards,

    Robert> Robert Marlow