From: Kevin Carhart <kevin@carhart.net>
To: Karl Dahlke <eklhad@comcast.net>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] seg fault in edbrowse proper
Date: Thu, 12 Jan 2017 11:18:31 -0800 (PST) [thread overview]
Message-ID: <alpine.LRH.2.03.1701121108240.29121@carhart.net> (raw)
In-Reply-To: <20170010083850.eklhad@comcast.net>
I pulled up the core dump from the issue raised by rawstory.com but am not
sure what it means. I think there is a bad string which can't be
processed by variants of printf. I don't know what the entry point is
from edbrowse files to system files.
After the first few below, it gives short entries like 4,5,6, forever.
#0 __GI__IO_default_xsputn (f=0x7ffda0961660, data=0x456080, n=0) at
genops.c:448
#1 0x00007f60f66ad867 in _IO_vfprintf_internal (s=s@entry=0x7ffda0961660,
format=format@entry=0x456080 "%c%d*", ap=ap@entry=0x7ffda0961778) at
vfprintf.c:1334
#2 0x00007f60f66d59f4 in __IO_vsprintf (string=0x7ffda0961860
"`>\346\001",
format=0x456080 "%c%d*", args=args@entry=0x7ffda0961778) at
iovsprintf.c:42
#3 0x00007f60f66b8127 in __sprintf (s=<optimized out>, format=<optimized
out>) at sprintf.c:32
#4 0x000000000042a39b in ?? ()
#5 0x000000000042a6d8 in ?? ()
#6 0x000000000043ccc7 in ?? ()
On Tue, 10 Jan 2017, Karl Dahlke wrote:
> Not the js process but edbrowse itself; though you have to have js active to get the seg fault.
>
> http://www.rawstory.com/2017/01/keith-olbermann-pleads-with-trump-supporters-his-illness-is-putting-your-family-at-risk
>
> Karl Dahlke
> _______________________________________________
> Edbrowse-dev mailing list
> Edbrowse-dev@lists.the-brannons.com
> http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev
>
--------
Kevin Carhart * 415 225 5306 * The Ten Ninety Nihilists
next prev parent reply other threads:[~2017-01-12 19:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-10 13:38 Karl Dahlke
2017-01-12 19:18 ` Kevin Carhart [this message]
2017-01-13 23:36 ` Chris Brannon
2017-01-14 2:49 ` Kevin Carhart
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=alpine.LRH.2.03.1701121108240.29121@carhart.net \
--to=kevin@carhart.net \
--cc=Edbrowse-dev@lists.the-brannons.com \
--cc=eklhad@comcast.net \
/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).