edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Kevin Carhart <kevin@carhart.net>
To: Karl Dahlke <eklhad@comcast.net>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] Stack smashing detected in jsrt
Date: Thu, 1 Oct 2015 16:25:44 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LRH.2.03.1510011556470.20360@carhart.net> (raw)
In-Reply-To: <20150830062758.eklhad@comcast.net>



Here is some more on jsrt crashing on Ubuntu.
I can even make this happen on a tiny, 6-line file, which is rather 
strange.
I kept taking things away and got it down to this.


<html>
<body>
<form onunload>
</form>
</body>
</html>

OR

<html>
<body>
<form onunload=formUnload(this.name)>
</form>
</body>
</html>

Regardless of whether or not there is a formUnload routine to go to.

Backtrace is included below.

In htmlParse, it is calling runOnload
The crash happens in runOnload.
I wasn't able to add any printf's to runOnload.
I think it's happening immediately upon entry into runOnload.

thanks
Kevin

xxxxxx

(gdb) bt
#0  0x00007fd8bd133f77 in __GI_raise (sig=sig@entry=6)
     at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#1  0x00007fd8bd1375e8 in __GI_abort () at abort.c:90
#2  0x00007fd8bd1714fb in __libc_message (do_abort=do_abort@entry=1,
     fmt=fmt@entry=0x7fd8bd282f10 "*** %s ***: %s terminated\n")
     at ../sysdeps/unix/sysv/linux/libc_fatal.c:199
#3  0x00007fd8bd20f08c in __GI___fortify_fail (msg=<optimized out>,
     msg@entry=0x7fd8bd282ef8 "stack smashing detected") at 
fortify_fail.c:37
#4  0x00007fd8bd20f030 in __stack_chk_fail () at stack_chk_fail.c:28
#5  0x000000000042dc69 in runOnload () at html.c:2008
#6  0x000000000042a805 in htmlParse (buf=0x243cb20 "", remote=0) at 
html.c:711
#7  0x00000000004152a8 in browseCurrentBuffer () at buffers.c:5328
#8  0x000000000041459a in runCommand (line=0x68e520 <line2.8236> 
"jsrt_crash")
     at buffers.c:4992
#9  0x0000000000414cee in edbrowseCommand (
     line=0x68c6a0 <line.8800> "b jsrt_crash", script=0 '\000')
     at buffers.c:5164
#10 0x0000000000406988 in main (argc=0, argv=0x7ffe2a9f2f10) at 
main.c:1364


      parent reply	other threads:[~2015-10-01 23:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-29 17:32 [Edbrowse-dev] jex debugger prints return values Karl Dahlke
2015-09-29 20:57 ` Kevin Carhart
2015-09-30  9:37 ` [Edbrowse-dev] Stack smashing detected in jsrt Kevin Carhart
2015-09-30 10:27   ` Karl Dahlke
2015-09-30 20:43     ` Kevin Carhart
2015-09-30 23:13       ` Karl Dahlke
2015-10-01 23:25     ` Kevin Carhart [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=alpine.LRH.2.03.1510011556470.20360@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).