zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: zsh 5.0.5-dev-2
Date: Sun, 17 Aug 2014 23:36:19 -0700	[thread overview]
Message-ID: <140817233619.ZM25264@torch.brasslantern.com> (raw)
In-Reply-To: <20140818025620.GA4198@localhost.localdomain>

On Aug 18, 10:56am, Han Pingtian wrote:
} Subject: Re: zsh 5.0.5-dev-2
}
} On Sun, Aug 17, 2014 at 10:30:30AM -0700, Bart Schaefer wrote:
} > 
} > I suspect Fortify is reporting a potential error rather than a real
} > one, because we'd presumably have seen other problems before this if
} > "cd .." actually caused an 8kb buffer on the stack to overflow.
} 
} I have tried to print the length of xbuf and *pp before the sprintf().
} Looks like when overflow being triggered, the length of xbuf is 8188,
} and the length of *pp is 10.

I must not previously have been understanding exactly what you tested.

I now suspect you've deliberately constructed and (with chaselinks not
set?) cd'd one level down at a time into a path that's at least 8188
characters long, and then setopt chaselinks and done "cd .." from the
bottom directory in that path.  Is that correct?

Maybe you previously posted exactly what test you were doing and I just
lost track of it.

Anyway, if that's along the lines of what you've done, then I retract
my "potential error rather than real" remark.


  reply	other threads:[~2014-08-18  6:36 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-12 20:29 Peter Stephenson
2014-08-12 22:36 ` Axel Beckert
2014-08-13 14:04   ` zsh 5.0.5-dev-2 / Occassional hangs on Test/A05execution.ztst Axel Beckert
2014-08-13 19:08     ` Bart Schaefer
2014-08-14  8:48       ` Axel Beckert
2014-08-14  8:50       ` Peter Stephenson
2014-08-14 16:25         ` Bart Schaefer
2014-08-14 16:31           ` Axel Beckert
2014-08-14 17:34             ` Axel Beckert
2014-08-15  4:50               ` Bart Schaefer
2014-08-15  9:32                 ` Axel Beckert
2014-08-15 17:33                   ` Bart Schaefer
2014-08-15 19:42                     ` Axel Beckert
2014-08-16 18:12                       ` zsh 5.0.5/6 Peter Stephenson
2014-08-13 17:28   ` zsh 5.0.5-dev-2 Dominic Hopf
2014-08-13 22:34 ` Oliver Kiddle
2014-08-14  8:34   ` Peter Stephenson
2014-08-14  9:32     ` Peter Stephenson
2014-08-14 16:20       ` Bart Schaefer
2014-08-14 19:54         ` Peter Stephenson
2014-08-15  4:44           ` Bart Schaefer
2014-08-15  8:38             ` Peter Stephenson
2014-08-15 11:23             ` Han Pingtian
2014-08-15 17:17               ` Bart Schaefer
2014-08-16  0:35                 ` Han Pingtian
2014-08-17 17:30                   ` Bart Schaefer
2014-08-18  2:56                     ` Han Pingtian
2014-08-18  6:36                       ` Bart Schaefer [this message]
2014-08-18 14:02                         ` Han Pingtian
2014-08-23 17:51                     ` Symlink chasing Peter Stephenson

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=140817233619.ZM25264@torch.brasslantern.com \
    --to=schaefer@brasslantern.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).