zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Markus Trippelsdorf <markus@trippelsdorf.de>, zsh-workers@zsh.org
Subject: Re: Two issues found with -fsanitize=undefined
Date: Thu, 17 Sep 2015 10:16:33 -0700	[thread overview]
Message-ID: <150917101633.ZM10051@torch.brasslantern.com> (raw)
In-Reply-To: <20150917075759.GA24365@x4>

On Sep 17,  9:57am, Markus Trippelsdorf wrote:
}
} I've build zsh trunk with -fsanitize=undefined and two issue popped up
} while running the testsuite:

It would be helpful if you included at least part of the output (after the
"for:") to indicate WHICH tests reported these errors.

} 1)
}  pattern.c:2645:12: runtime error: signed integer overflow: 1234567890123456789 * 10 cannot be represented in type 'long int'

That one is fairly easy to recognize (the string 1234567890123456789 is
in the test case itself) but this one:

}  compmatch.c:341:6: runtime error: null pointer passed as argument 2, which is declared to never be null}
} Test ./Y02compmatch.ztst failed: output differs from expected as shown above for:

Could be anything.  The error indicates that "matchbuf" is NULL at the
point where we expect to copy it into a new buffer, but if there is a
deeper reason why that is unexpectedly NULL it would be better to fix
that than to simply skip the copy.


  reply	other threads:[~2015-09-17 17:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-17  7:57 Markus Trippelsdorf
2015-09-17 17:16 ` Bart Schaefer [this message]
2015-09-17 17:24   ` Markus Trippelsdorf
2015-09-17 17:41     ` Bart Schaefer
2015-09-19 19:57 ` Peter Stephenson
2015-09-19 20:18   ` Markus Trippelsdorf
2015-09-19 22:35     ` Peter Stephenson
2015-09-20  4:09       ` Bart Schaefer
2015-09-21 12:46   ` Peter Stephenson
2015-09-21 19:13 ` Peter Stephenson
2015-09-21 20:04   ` Markus Trippelsdorf
2015-09-21 20:21     ` Peter Stephenson
2015-09-21 20:34       ` Markus Trippelsdorf
2015-09-21 20:56         ` Bart Schaefer
2015-09-22  0:02           ` Markus Trippelsdorf

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=150917101633.ZM10051@torch.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=markus@trippelsdorf.de \
    --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).