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 seg fault
Date: Wed, 14 Jan 2015 07:05:46 -0500	[thread overview]
Message-ID: <20150014070546.eklhad@comcast.net> (raw)

If you would pull the latest, and then see if you can reproduce my seg fault,
because it is very very strange.
I think it's another curl thing so hoping Chris can help me here.

First, my latest push fixes a small bug wherein
r filename
would offer to download that file in certain cases.
But if you are commanding to read it into the buffer
then you never want to download it.
That was a one line fix, but did not fix or affect the following bug.

Bring up edbrowse with no args, an empty buffer, and then

r https://login.persona.org/include.js

Type qt to quit, bypassing as much machinery as possible.
seg fault.

This test does not involve javascript at all,
the process is never launched.

The seg fault goes away if you comment out the line
        curl_global_cleanup();
in main.c line 933.

Here's the interesting part; the seg fault also goes away, at least for me,
if you type vs first.
Don't verify certificates.
Read in the file as usual, and quit, and all is well.
What's up with that???
It means if you can't reproduce it it might depend on my local cert file.
It might depend on a lot of things.
Wonder if it is yet another bug in my somewhat older open ssl,
but damnit it's not that much older!

An unrelated question: bgl tracks and displays background downloads,
should it also track and display foreground downloads?
Obviously none of these will ever be in the in progress state.

Karl Dahlke

             reply	other threads:[~2015-01-14 12:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-14 12:05 Karl Dahlke [this message]
2015-01-14 12:33 ` Chris Brannon
2015-01-15 15:21 ` Adam Thompson
2015-01-15 15:27 ` [Edbrowse-dev] bgl command Adam Thompson

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=20150014070546.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).