Opened 20 years ago

Closed 20 years ago

Last modified 20 years ago

#3127 closed defect (wontfix)

tin crashes when reading article

Reported by: arthur@… Owned by: matt@…
Priority: Normal Milestone:
Component: base Version: 1.0
Keywords: Cc:
Port:

Description

tin works fine up to the point where I read an article:

rtin -g news.game.org -f .newsrc_gmane

(start, pick a news group, use tab to read first unread article)

rtin: assertion failure: ./thread.c (997): i != oldirticles *

Exactly the same happens when using tin -r instead of rtin.

tin 1.6.2 release 20030910 ("Pabbay") [UNIX] (c) Copyright 1991-2003 Iain Lea.

kremer:~ $ uname -a Darwin kremer.york.ac.uk 8.1.0 Darwin Kernel Version 8.1.0: Tue May 10 18:16:08 PDT 2005; root:xnu-792.1.5.obj~4/RELEASE_PPC Power Macintosh powerpc

(OS X 10.4.1)

Change History (3)

comment:1 Changed 20 years ago by jmpp@…

Owner: changed from darwinports-bugs@… to matt@…

comment:2 Changed 20 years ago by matt@…

Resolution: wontfix
Status: newclosed

Hi,

As i don't have any access to a Mac OS X 10.4.x nor a Darwin 8.x based machine, i'm afraid i can't easily fix this, sorry. FYI, some others Tiger users have reported issues while using tin on Mac OS X 10.4.x / Darwin 8.x on tin's mailing list. You may join it to get any news on having tin working on this system.

comment:3 Changed 20 years ago by matt@…

Arthur, You're lucky, as Paul Mason have fix this issue (check the transcript below from tin's list):

==========>8========== 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. ==========>8==========

hope this helps.

Note: See TracTickets for help on using tickets.