Re: [tin] Tin Quits when reading a message

On 17 May 2005, at 11:00, Paul Mason wrote:

> First, apologies if this is a duplicate. I posted this via Google
> groups yesterday but I'm not sure if that gets forwarded to this list
> or not.
>
> I've just upgraded to Mac OS X 10.4 ("Tiger") and started using tin
> again after having not used it for a while. However I've found that
> whenever I try to read a message it quits out of tin. This happens
> whether I use space to read the next unread, or press enter or
> right-arrow when the message is highlighted.
>
> This is the case with the Darwin Ports version 1.6.2 and 1.7.8 which I
> built from sources on tin.org.
>
> I used to use tin some time ago (on 10.3) and I don't remember having
> this problem. However it's possible that it's a configuration thing
> that I changed and forgot about.
>
> Anyone any thoughts on what might cause this?
>
> Thanks
> --  
> Paul Mason
>
>

So I figured it out eventually.

Running tin with ktrace and then running kdump showed this

        "tin: assertion failure: ./thread.c (1000): i != oldi
        "

So I checked thread.c line 1000

         for_each_art_in_thread(i, n) {
                 assert(i != ART_EXPIRED);
                 assert(i != oldi);
                 oldi = i;
                 sum++;
         }

Looks fine. After some messing around and some googling I found that  
there seems to be a bug in gcc 4.0. The odd thing was that when I put  
in some of my own debug to print out the values of i etc - it  
compiled ok. But I didn't trust it so I recompiled with gcc 3.3.

Anyway, all seems to be working now.

Posting this in case it helps someone else.

-- 
Paul Mason