zsh-workers
 help / color / mirror / code / Atom feed
From: Sebastian Gniazdowski <psprint2@fastmail.com>
To: zsh-workers@zsh.org
Subject: Re: [PATCH] db/gdbm rewrite
Date: Thu, 16 Feb 2017 08:25:24 -0800	[thread overview]
Message-ID: <1487262324.1911841.883231656.222E231A@webmail.messagingengine.com> (raw)
In-Reply-To: <1487261017.1907093.883202288.270632CF@webmail.messagingengine.com>

On Thu, Feb 16, 2017, at 08:03 AM, Sebastian Gniazdowski wrote:
> On Thu, Feb 16, 2017, at 07:11 AM, Peter Stephenson wrote:
> > % zmodload zsh/db/gdbm
> > % ztie -d db/gdbm -f db.gdbm dbase
> > % dbase[testkey]=somewhat
> > ==25034== Invalid write of size 1
> > ==25034==    at 0x80E0B78: metafy (utils.c:4652)
> 
> I've used HEAP_ALLOC instead of HEAP_DUP in argument for metafy. Fixing
> this resolves valgrind report. Important catch.. Hopefully it will
> resolve enable-zsh-mem problem (I cannot reproduce that). Sending as
> complete patch plus db_gdbm.c file.

Yeah this will fix the problem. I did:

        pm->u.str = metafy(content.dptr, content.dsize, META_ALLOC);

There were no meta characters so metafy() didn't allocate memory,
returned internal GDBM  pointer. META_DUP always allocates. Thanks!

-- 
Sebastian Gniazdowski
psprint2@fastmail.com


  reply	other threads:[~2017-02-16 16:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-14 12:20 Sebastian Gniazdowski
2017-02-15 10:22 ` Sebastian Gniazdowski
2017-02-16 10:16   ` Peter Stephenson
2017-02-16 11:46     ` Sebastian Gniazdowski
2017-02-16 12:52       ` Peter Stephenson
2017-02-16 14:25         ` Sebastian Gniazdowski
2017-02-16 14:30           ` Sebastian Gniazdowski
2017-02-16 15:11             ` Peter Stephenson
2017-02-16 16:03               ` Sebastian Gniazdowski
2017-02-16 16:25                 ` Sebastian Gniazdowski [this message]
2017-02-16 16:36                   ` Peter Stephenson
2017-02-16 17:12                     ` Sebastian Gniazdowski
2017-02-16 18:16                 ` Sebastian Gniazdowski
2017-02-19  0:43 (Fwd) " Bart Schaefer
2017-02-19  8:46 ` Sebastian Gniazdowski
2017-02-19 18:19   ` Bart Schaefer
2017-02-20  8:32     ` Sebastian Gniazdowski

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=1487262324.1911841.883231656.222E231A@webmail.messagingengine.com \
    --to=psprint2@fastmail.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).