From: Adam Thompson <arthompson1990@gmail.com>
To: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] js progress update
Date: Wed, 8 Jan 2014 10:03:04 +0000 [thread overview]
Message-ID: <20140108100304.GA3935@toaster.adamthompson.me.uk> (raw)
In-Reply-To: <20140107121041.GK11201@toaster.adamthompson.me.uk>
On Tue, Jan 07, 2014 at 12:10:41PM +0000, Adam Thompson wrote:
> On Tue, Jan 07, 2014 at 12:08:17PM +0000, Adam Thompson wrote:
> > PS: if you want to see the progress, the repo is at:
> > https://github.com/arthompson/edbrowse.git
>
> Yes, I know I need to run ebindent over everything,
> but I was leaving tidying up formatting till I'd finished making large changes.
Ok, I've got a version which builds and runs with my compiled version of mozjs
24 (with --enable-optimize and --disable-debug)
but which segfaults when built against the Debian supplied package.
No idea why this may be, and even with the debugging symbols (libmozjs24d-dbg)
installed it doesn't give me enough info to work out what's breaking.
What I really need to know is how the debian libmozjs24d package is compiled on
amd64 (the architecture of my development box)
so I can check if this is an edbrowse issue or a libmozjs24d debian package issue.
Anyone out there know (or know how I can find out)?
Cheers,
Adam.
next prev parent reply other threads:[~2014-01-08 10:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-07 12:08 Adam Thompson
2014-01-07 12:10 ` [Edbrowse-dev] js progress update1 Adam Thompson
2014-01-08 10:03 ` Adam Thompson [this message]
2014-01-08 11:05 [Edbrowse-dev] js progress update Karl Dahlke
2014-01-08 12:40 ` Adam Thompson
2014-01-14 20:43 ` Chris Brannon
2014-01-14 21:27 ` Adam Thompson
2014-01-14 22:17 ` Chris Brannon
2014-01-17 12:09 ` Adam Thompson
2014-01-17 18:42 ` Chris Brannon
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=20140108100304.GA3935@toaster.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).