From: Adam Thompson <arthompson1990@gmail.com>
To: edbrowse-dev@edbrowse.org
Subject: [edbrowse-dev] Abort from within duktape when visiting https://www.digicatapult.org.uk/careers
Date: Sat, 7 Dec 2019 17:28:53 +0000 [thread overview]
Message-ID: <20191207172853.GB194728@toaster> (raw)
Hi all,
As per the subject really. This blew up with both my older compiled version
of duktape and the version from Debian sid. I'd give a full backtrace but
I'm lacking a duktape with debug symbols (how do I get this) and thus the
interesting part disappears (see below for what I have):
b https://www.digicatapult.org.uk/careers
[New Thread 0x7ffff6c73700 (LWP 293666)]
[Thread 0x7ffff6c73700 (LWP 293666) exited]
119328
[New Thread 0x7ffff6c73700 (LWP 293667)]
[Thread 0x7ffff6c73700 (LWP 293667) exited]
[New Thread 0x7ffff6c73700 (LWP 293668)]
[Thread 0x7ffff6c73700 (LWP 293668) exited]
[New Thread 0x7ffff6c73700 (LWP 293669)]
[New Thread 0x7ffff61c1700 (LWP 293670)]
[New Thread 0x7ffff59c0700 (LWP 293671)]
[New Thread 0x7ffff51bf700 (LWP 293672)]
[Thread 0x7ffff51bf700 (LWP 293672) exited]
[Thread 0x7ffff6c73700 (LWP 293669) exited]
[Thread 0x7ffff61c1700 (LWP 293670) exited]
[Thread 0x7ffff59c0700 (LWP 293671) exited]
Thread 1 "edbrowse" received signal SIGABRT, Aborted.
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
50 ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1 0x00007ffff7a22535 in __GI_abort () at abort.c:79
#2 0x00007ffff7d2ccf6 in ?? () from
/usr/lib/x86_64-linux-gnu/libduktape.so.204
#3 0x00007ffff7d35649 in duk_fatal_raw () from
/usr/lib/x86_64-linux-gnu/libduktape.so.204
#4 0x00007ffff7d4849b in ?? () from
/usr/lib/x86_64-linux-gnu/libduktape.so.204
#5 0x00007ffff7d39929 in ?? () from
/usr/lib/x86_64-linux-gnu/libduktape.so.204
#6 0x00007ffff7d2ce16 in ?? () from
/usr/lib/x86_64-linux-gnu/libduktape.so.204
#7 0x00007ffff7d369fb in ?? () from
/usr/lib/x86_64-linux-gnu/libduktape.so.204
#8 0x00007ffff7d36a8c in ?? () from
/usr/lib/x86_64-linux-gnu/libduktape.so.204
#9 0x00005555555d6494 in set_property_string_nat (parent=0x555555ac8268,
name=0x5555555d9e3d "readyState", value=0x5555555d9e34 "complete") at
jseng-duk.c:1839
#10 0x00005555555ae57a in set_property_string (obj=0x555555ac8268,
name=0x5555555d9e3d "readyState", value=0x5555555d9e34 "complete") at
ebjs.c:416
#11 0x000055555559d452 in htmlParse (buf=0x555555d267e0 "", remote=1) at
html.c:926
#12 0x000055555558dd95 in browseCurrentBuffer () at buffers.c:6757
#13 0x000055555558ce61 in runCommand (line=0x555555bc6c12
"https://www.digicatapult.org.uk/careers") at buffers.c:6383
#14 0x000055555558d6f4 in edbrowseCommand (line=0x555555bc6c10 "b
https://www.digicatapult.org.uk/careers", script=0 '\000') at buffers.c:6573
#15 0x0000555555578db2 in inputForever (ptr=0x0) at main.c:904
#16 0x0000555555578d3d in main (argc=0, argv=0x7fffffffea30) at main.c:890
(gdb)
Sorry for the second post in an hour and for neither of them actually
containing a full fix.
Cheers,
Adam.
next reply other threads:[~ UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
Adam Thompson [this message]
` Karl Dahlke
` Adam Thompson
` [edbrowse-dev] Abort from within duktape when visiting Karl Dahlke
` Adam Thompson
` Karl Dahlke
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=20191207172853.GB194728@toaster \
--to=arthompson1990@gmail.com \
--cc=edbrowse-dev@edbrowse.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).