public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/18333] FAIL: timezone/tst-tzset (segmentation fault)
Date: Mon, 27 Apr 2015 13:56:00 -0000	[thread overview]
Message-ID: <bug-18333-131-UXvpOan9cI@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-18333-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=18333

--- Comment #2 from Florian Weimer <fweimer at redhat dot com> ---
There are multiple issues here: a crash after a memory allocation failure in
tzset (which somehow appears to occur under valgrind).  In addition, the
tst-tzset test case contains an ill-fated attempt to avoid the create_temp_file
memory leak.  I'll fix the test harness to support this use case (existing code
will observe no difference).

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2015-04-27 13:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-26 13:48 [Bug libc/18333] New: " hjl.tools at gmail dot com
2015-04-26 13:49 ` [Bug libc/18333] " hjl.tools at gmail dot com
2015-04-26 14:16 ` hjl.tools at gmail dot com
2015-04-27 13:27 ` fweimer at redhat dot com
2015-04-27 13:56 ` fweimer at redhat dot com [this message]
2015-04-27 14:28 ` fweimer at redhat dot com
2015-04-27 14:52 ` hjl.tools at gmail dot com
2015-04-27 16:24 ` hjl.tools at gmail dot com
2015-04-27 17:07 ` hjl.tools at gmail dot com
2015-04-27 17:44 ` fweimer at redhat dot com
2015-04-27 17:44 ` fweimer at redhat dot com

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=bug-18333-131-UXvpOan9cI@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.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. 
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 read-only IMAP folder(s) and NNTP newsgroup(s).