Re: Thread + Socket + Pipes Bug?

[Robert Marlow]

Ok, got 1.7 installed. No go though - for me it just segfaults as soon
as the client closes the TCP port. strace gives me this at the end:
read(6, "", 1)                          = 0
shutdown(6, 2 /* send and receive */)   = 0
kill(23511, SIGRTMIN)                   = 0
kill(23511, SIGRTMIN)                   = 0
select(6, [5], [], [], NULL)            = ? ERESTARTNOHAND (To be
restarted)
--- SIGSEGV (Segmentation fault) ---
+++ killed by SIGSEGV +++

--debug for guile gives me nada. 

I'm thinking I'll leave that one alone for now and figure out what's
going on with 1.6.3/4. Since I'm using 1.6.3 and 1.6.4 it's strange that
your pre-1.6.4 release version right between the two releases I'm using
isn't displaying the same bug. It's gotta be something else you've got
that I don't...


On Wed, 2003-08-13 at 07:06, Neil Jerram wrote:
> >>>>> "bobstopper" == bobstopper  <address@hidden> writes:
> 
>     bobstopper> Ok, well that's pretty annoying. That's certainly what
>     bobstopper> I do to get it complaining. [...] Do you have anything
>     bobstopper> related installed which might be working around the
>     bobstopper> problem?
> 
> Well I'm actually using the 1.6.x CVS branch as it was shortly before
> the 1.6.4 release.  (It seems impossible right now to get a 1.6.4
> release - according to GNU and mirror sites it is being checked for
> authenticity...?)  Other than that my box is a standard GNU/Linux.
> 
> Do you happen to know whether the problem repros on any other Guile
> releases, or on the 1.7.x CVS branch?
> 
>         Neil
-- 
Regards,

Robert Marlow