Bump version for release

This release fixes the handling of a server HTTP 304 response, now treating it as non-fatal.
Treat HTTP 304 codes as non-fatal
2026-09-06 13:51:38 +00:00 · 2015-10-02 12:15:07 -07:00 · 2015-10-02 12:15:02 -07:00 · 2015-10-02 10:36:39 -07:00
3 changed files with 10 additions and 2 deletions
@@ -20,3 +20,5 @@ install-sh
 missing
 stamp-h1
 *.tar.gz
+tags
+cscope.*
@@ -2,7 +2,7 @@
 # Process this file with autoconf to produce a configure script.

 AC_PREREQ([2.66])
-AC_INIT(clr-debug-info, 21, arjan@linux.intel.com)
+AC_INIT(clr-debug-info, 22, arjan@linux.intel.com)
 AM_INIT_AUTOMAKE([foreign -Wall -W subdir-objects])
 AM_SILENT_RULES([yes])
 AC_PROG_CC
@@ -122,7 +122,13 @@ static int curl_get_file(const char *url, const char *prefix, time_t timestamp)
 	fflush(file);
 //	printf("HTTP return code is %i\n", ret);

-	if (ret != 200 && ret != 404)
+	/* HTTP 304 is returned if (a) the cached debuginfo has the same
+	 * timestamp or is newer than that on the server and (b) we haven't
+	 * already added the URL to the hash table. So, the first crash for a
+	 * boot may result in a 304 if the debuginfo had been downloaded in a
+	 * previous boot.
+	 */
+	if (ret != 200 && ret != 404 && ret != 304)
 		urlcounter++;

 	if (ret == 200) {