zsh-workers
 help / color / mirror / code / Atom feed
From: DragonK <dragonk@gmail.com>
To: Peter Stephenson <pws@csr.com>
Cc: zsh-workers@sunsite.dk
Subject: Re: Buffer overflow in "!" handling?
Date: Wed, 25 Feb 2009 13:39:36 +0200	[thread overview]
Message-ID: <8fa12ca90902250339n10d7ee9qecd03b0097b3d9a5@mail.gmail.com> (raw)
In-Reply-To: <20090225102603.089bc856@news01>

>
> You're right, that's nasty.  See if you can get it to happen with this...
>

I've applied the patch and it seems to work now; as far as I
understand from the comments in mem.c, memory allocated with zhalloc()
doesn't need to be explicitly free()d, right?


  reply	other threads:[~2009-02-25 11:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-25  9:42 DragonK
2009-02-25 10:26 ` Peter Stephenson
2009-02-25 11:39   ` DragonK [this message]
2009-02-25 11:42     ` 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=8fa12ca90902250339n10d7ee9qecd03b0097b3d9a5@mail.gmail.com \
    --to=dragonk@gmail.com \
    --cc=pws@csr.com \
    --cc=zsh-workers@sunsite.dk \
    /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).