edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Karl Dahlke <eklhad@comcast.net>
To: edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] Curl library error
Date: Mon, 29 Jan 2018 11:03:59 -0500	[thread overview]
Message-ID: <20180029110359.eklhad@comcast.net> (raw)
In-Reply-To: <alpine.DEB.2.21.1801290708190.1843@debian.pulsar.com>

[-- Attachment #1: Type: text/plain, Size: 876 bytes --]

Someone on stack overflow says that error is typically caused by a callback returning the wrong / unexpected number of bytes.
These callbacks are at http.c line 2069 and line 299.
Not sure how either of these functions could return the wrong number of bytes (assuming you're not downloading a page directly to disk, with not enough room on disk, which is really unlikely).
Very first line computes the number of bytes to return.
If the bug were here I might put in some prints to see the arguments and the bytes returned.

Or you might use git to back up a couple weeks,
although nothing we've done in the past month has touched that file, so that's a longshot.

git checkout df7c3d74890026fc1acbfabdbb5a7b82c12cbc4d

It will yammer about a detatched head.
Rebuild and test. But make sure you

git checkout master

to get back to current code.

Karl Dahlke

  parent reply	other threads:[~2018-01-29 16:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-29 12:09 Chuck Hallenbeck
2018-01-29 14:06 ` Karl Dahlke
2018-01-29 15:19   ` Chuck Hallenbeck
2018-01-29 15:27   ` Chuck Hallenbeck
2018-01-29 16:03 ` Karl Dahlke [this message]
2018-01-29 16:53   ` Chuck Hallenbeck
2018-01-29 17:37     ` Dominique Martinet
     [not found] ` <alpine.DEB.2.21.1802010449280.1929@debian.pulsar.com>
2018-02-01 18:08   ` Karl Dahlke

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180029110359.eklhad@comcast.net \
    --to=eklhad@comcast.net \
    --cc=edbrowse-dev@lists.the-brannons.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).