I have also been working in my spare time on packaging rssowl for FC5 [sic]. I can post my .spec file if wanted. Here's my list of unfixed libgcj bugs that need to be fixed before rssowl will run natively reliably. These are both threading bugs. 1. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22211 "Thread.interrupt sometimes causes abort if thread is already dead" This gets hits about 25%-50% of the time on quitting rssowl, and occassionaly also when I press the little red stop button at the bottom of the window. I can provide a backtrace if wanted. Unfortunately rssowl only saves any changes upon quit, so this means that any changes (including preferences and even the record of which feed items have been read) will be lost 25-50% of the time - unacceptable, obviously. 2. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13212 "AttachCurrentThread() not working" This is an old bug. It only triggered for me once I rebuilt gcc for Athlon (32bit) with a private threading patch, but now it triggers 100% of the time, every time I try to view the Dilbert comic in rssowl. Again, backtrace available on request. I am convinced that it is a real bug in the existing code, not a bug in my patch. After all, bad memory accesses don't always trigger SIGSEGVs. Sometimes they just cause memory corruptions. So probably, previously it was just causing memory corruptions instead of SIGSEGVs for some subtle reason. Feel free to add to this list. -- Robin
