From: Adam Thompson <arthompson1990@gmail.com>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] segfault in latest Edbrowse
Date: Thu, 4 Feb 2016 20:37:41 +0000 [thread overview]
Message-ID: <20160204203741.GA6810@122oven.adamthompson.me.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 351 bytes --]
Hi all,
I updated my various copies of Edbrowse today and noticed that it appears
there's now a segfault, in particular I noticed it when viewing questions on
stack overflow (and other sites using that platform).
I'm happy to have a go at debugging this but was wondering how one gets a debug
build with our cmake based build system?
Cheers,
Adam.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next reply other threads:[~2016-02-04 20:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-04 20:37 Adam Thompson [this message]
2016-02-05 5:28 ` Karl Dahlke
2016-02-05 6:47 ` Chris Brannon
2016-02-05 9:25 ` Chris Brannon
2016-02-05 13:59 ` Karl Dahlke
2016-02-05 14:21 ` Geoff McLane
2016-02-06 11:57 ` Adam Thompson
2016-02-06 12:03 ` 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=20160204203741.GA6810@122oven.adamthompson.me.uk \
--to=arthompson1990@gmail.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).