zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <p.stephenson@samsung.com>
To: zsh-workers@zsh.org
Subject: Re: Bug with long multiline strings?
Date: Wed, 24 Oct 2012 17:10:23 +0100	[thread overview]
Message-ID: <20121024171023.313995d7@pwslap01u.europe.root.pri> (raw)
In-Reply-To: <87vcdzq4ke.fsf@ft.bewatermyfriend.org>

On Wed, 24 Oct 2012 17:21:05 +0200
Frank Terbeck <ft@bewatermyfriend.org> wrote:
> Hi workers!
> 
> I've tried to reproduce
> 
>   <https://bugs.launchpad.net/ubuntu/+source/zsh/+bug/1070820>
> 
> 
> Turns out, I can:
> 
> [snip]
> i-(6000)-~% echo "asdf
> dquote> asdf
> dquote> asdf
> dquote> asdf
> dquote> asdf
> dquote> asfd
> dquote> asdf
> dquote> asdf
> dquote> asdf
> dquote> asdf
> dquote> asdf
> dquote> asdf
> dquote> asdf
>  mem.c:604: BUG: hrealloc() called for non-heap memory.
> [1]    2554 segmentation fault (core dumped)  zsh
> [snap]

Something very funny is going on here.  That's basic shell allocation
stuff that's failing, which gets used all the time.  Also, it shouldn't
need to reallocate at all until there are 256 characters in the input
token, which you haven't got close to.  There are no interrupts or
recursion involved.

Looks like there's a Mystery Ingredient.

pws


  reply	other threads:[~2012-10-24 16:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-24 15:21 Frank Terbeck
2012-10-24 16:10 ` Peter Stephenson [this message]
2012-10-24 16:31   ` Peter Stephenson
2012-10-25  8:59   ` Peter Stephenson
2012-10-25  9:21     ` Frank Terbeck
2014-01-17 20:24       ` Frank Terbeck
2014-01-18 21:34         ` Bart Schaefer
2014-01-19  4:59           ` Bart Schaefer
2014-01-19 11:28             ` Frank Terbeck
2014-01-19 12:01             ` Bug reports after releases (was: Re: Bug with long multiline strings?) Axel Beckert

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=20121024171023.313995d7@pwslap01u.europe.root.pri \
    --to=p.stephenson@samsung.com \
    --cc=zsh-workers@zsh.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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).