From: Isaac Dunham <ibid.ag@gmail.com>
To: musl@lists.openwall.com, alpine-devel@lists.alpinelinux.org
Subject: Re: webkitfltk segfaults in do_relocs (partly solved)
Date: Fri, 21 Nov 2014 21:24:31 -0800 [thread overview]
Message-ID: <20141122052430.GB28486@newbook> (raw)
In-Reply-To: <20141119164412.GB16895@newbook>
Hello,
Thanks for all the advice. Now it gets a lot further:
I built webkitfltk with -fno-pie, and the test program loaded, showed
a window, and crashed somewhere in JavaScriptCore.
I tried running Source/JavaScriptCore/jsc, and it shows a problem that
was previously reported:
$ Source/JavaScriptCore/jsc
Error compiling builtin:
ASSERTION FAILED: result
parser/Parser.h(970) : WTF::PassRefPtr<T> JSC::parse(JSC::VM*, const JSC::SourceCode&, JSC::FunctionParameters*, const JSC::Identifier&, JSC::JSParserStrictness, JSC::JSParserMode, JSC::ParserError&, JSC::JSTextPosition*) [with ParsedNode = JSC::ProgramNode]
Segmentation fault (core dumped)
Upstream has set thread stack size to 1 megabyte regardless of libc,
figuring that 8 megabytes is too much.
I'm building with -DUSE_SYSTEM_MALLOC=1.
Looking through the old thread on Webkit javascript crashing, I found an
excerpt of a diff, but could not figure out where it's supposed to apply
(grep -r didn't find anything pertinent that I could see).
Thanks,
Isaac Dunham
---
Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org
Help: alpine-devel+help@lists.alpinelinux.org
---
prev parent reply other threads:[~2014-11-22 5:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-19 16:44 webkitfltk segfaults in do_relocs Isaac Dunham
2014-11-19 16:50 ` Rich Felker
2014-11-19 19:04 ` Isaac Dunham
2014-11-19 19:13 ` Rich Felker
2014-11-19 19:48 ` Isaac Dunham
2014-11-19 19:58 ` Rich Felker
2014-11-19 20:20 ` Isaac Dunham
2014-11-19 20:56 ` Rich Felker
2014-11-19 22:43 ` Isaac Dunham
2014-11-20 6:14 ` Timo Teras
2014-11-22 5:24 ` Isaac Dunham [this message]
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=20141122052430.GB28486@newbook \
--to=ibid.ag@gmail.com \
--cc=alpine-devel@lists.alpinelinux.org \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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).