From: Adam Thompson <arthompson1990@gmail.com>
To: Karl Dahlke <eklhad@comcast.net>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] curl seg fault
Date: Thu, 15 Jan 2015 15:21:02 +0000 [thread overview]
Message-ID: <20150115152102.GA24402@toaster.adamthompson.me.uk> (raw)
In-Reply-To: <20150014070546.eklhad@comcast.net>
[-- Attachment #1: Type: text/plain, Size: 545 bytes --]
On Wed, Jan 14, 2015 at 07:05:46AM -0500, Karl Dahlke wrote:
> 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.
I can't reproduce this either. I suspect you've just got a broken openssl,
or your version of curl has problems working with your version of openssl.
If I were you I'd seriously consider upgrading.
What distro do you run and do they package an up-to-date openssl and curl?
Cheers,
Adam.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-01-15 15:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-14 12:05 Karl Dahlke
2015-01-14 12:33 ` Chris Brannon
2015-01-15 15:21 ` Adam Thompson [this message]
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=20150115152102.GA24402@toaster.adamthompson.me.uk \
--to=arthompson1990@gmail.com \
--cc=Edbrowse-dev@lists.the-brannons.com \
--cc=eklhad@comcast.net \
/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).