zsh-workers
 help / color / mirror / code / Atom feed
From: Michael Hwang <michael.a.hwang@gmail.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: LinkList implementation
Date: Sat, 27 Feb 2010 17:33:24 -0500	[thread overview]
Message-ID: <22a0ef081002271433u713e1923lb04c7d1bf369d3d0@mail.gmail.com> (raw)

In the process of writing a new builtin, I discovered an oddity of
zsh's implementation of LinkList, which is a doubly linked list.

LinkList alist = newlinklist();
LinkNode node;
for (node = lastnode(alist); node; decnode(alist)) {
     ((SomeStructPointer) getdata(node))->someField;
}

Since no nodes have been added to the LinkList, one would expect the
body of the loop to not run at all. However, it does, and crashes
because attempting to access someField dereferences a null pointer. I
think this is due to this line in [z]newlinknode():

list->list.last = &list->node;

I'm not exactly sure why LinkLists are set up this way; I assume it's
a tricky way to allow [z]insertlinknode() to be used in the pushnode()
macro. However, this makes the lastnode() macro return non-null on an
empty LinkList. Walking backwards along a LinkList is only done once
in the entirety of zsh (the decnode() macro is only used once), which
is why I think no one has run into this bug before. I'm hoping someone
who has a better understanding of LinkLists can fix this.

Michael Hwang


             reply	other threads:[~2010-02-27 22:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-27 22:33 Michael Hwang [this message]
2010-02-27 22:45 ` Michael Hwang
2010-02-28  9:06 ` Andrey Borzenkov
2010-03-01 18:00   ` Michael Hwang
2010-03-01 18:12     ` Peter Stephenson
2010-03-06  3:48       ` [PATCH] Added LinkList documentation to linklist.c Michael Hwang
2010-03-07 21:36         ` 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=22a0ef081002271433u713e1923lb04c7d1bf369d3d0@mail.gmail.com \
    --to=michael.a.hwang@gmail.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).