You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Cannot be parsed. It halts in debug mode with EXC_BAD_ACCESS.
Following is the debug run output:
run
[Switching to process 10709]
Running…
Program received signal: “EXC_BAD_ACCESS”.
sharedlibrary apply-load-rules all
kill
quit
This is actually two issues in one. The first issue is that aborting the parse can cause objects to be freed prematurely. The second is that the RSS feed uses a date format that doesn't appear to conform to RFC822 and we don't handle its particular variety yet.
Support odd date format used by Google News (closed by ad8e8a8)
Google News has a weird quirk with its RSS dates where it gives
every date both a textual timezone as well as a numeric one.
In addition, it adds a separator between the hours and minutes
in the numeric timezone. Neither of these quirks are RFC822-compliant.
We should support them anyway.
http://news.google.com/news?output=rss
Cannot be parsed. It halts in debug mode with EXC_BAD_ACCESS.
Following is the debug run output:
run
[Switching to process 10709]
Running…
Program received signal: “EXC_BAD_ACCESS”.
sharedlibrary apply-load-rules all
kill
quit
And the code I tested is following:
The text was updated successfully, but these errors were encountered: