From: Chris Brannon <chris@the-brannons.com>
To: edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] curl seg fault
Date: Wed, 14 Jan 2015 04:33:55 -0800 [thread overview]
Message-ID: <87387dbky4.fsf@the-brannons.com> (raw)
In-Reply-To: <20150014070546.eklhad@comcast.net> (Karl Dahlke's message of "Wed, 14 Jan 2015 07:05:46 -0500")
Karl Dahlke <eklhad@comcast.net> writes:
> It might depend on a lot of things.
> Wonder if it is yet another bug in my somewhat older open ssl,
I can't reproduce this, go figure.
-- Chris
next prev parent reply other threads:[~2015-01-14 12:36 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 [this message]
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=87387dbky4.fsf@the-brannons.com \
--to=chris@the-brannons.com \
--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).