Bug#350779: liferea: Crashes on specific feed

2006-02-09 Thread David Moreno Garza
On 09:09 Thu 09 Feb 2006, Sebastian Dröge wrote: > Am Donnerstag, den 09.02.2006, 00:18 -0500 schrieb Nathan Conrad: > > I found the reason for the crash. It can be fixed by doing a string > > substitute in the atom10.c file: > > > > Change "struct atom10ParserState state" to > >"struct at

Bug#350779: liferea: Crashes on specific feed

2006-02-09 Thread Sebastian Dröge
Am Donnerstag, den 09.02.2006, 00:18 -0500 schrieb Nathan Conrad: > I found the reason for the crash. It can be fixed by doing a string > substitute in the atom10.c file: > > Change "struct atom10ParserState state" to >"struct atom10ParserState *state". After that, everything > should work

Bug#350779: liferea: Crashes on specific feed

2006-02-08 Thread Nathan Conrad
I found the reason for the crash. It can be fixed by doing a string substitute in the atom10.c file: Change "struct atom10ParserState state" to "struct atom10ParserState *state". After that, everything should work. This fix will be released in 1.0.4. -Nathan On Mon, Feb 06, 2006 at 08:30:

Bug#350779: liferea: Crashes on specific feed

2006-02-06 Thread Sebastian Dröge
Hi, I still get this crash with 1.0.3-1 on ppc with _every_ atom feed, for example this one: http://slomosnail.de/feeds/atom10.xml This is the backtrace I get (liferea compiled with "nostrip debug"): > Program received signal SIGSEGV, Segmentation fault. > [Switching to Thread 805506928 (LWP 3310

Bug#350779: liferea: Crashes on specific feed

2006-01-31 Thread Matijs van Zuijlen
Package: liferea Version: 1.0.2-1 Severity: normal Since today, when updating the feed http://www.allinthehead.com/atom/index.php, liferea crashes. I have produced the following backtrace with gdb: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 805437312 (LWP 7906)]