public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Stefan Liebler <stli@linux.ibm.com>
To: libc-alpha@sourceware.org
Subject: Re: Question regarding failing xcheck posix/bug-ga2-mem and resolv/mtrace-tst-leaks2 on Fedora 33
Date: Tue, 17 Nov 2020 09:36:09 +0100	[thread overview]
Message-ID: <82873473-2595-3934-74db-4570eaacc4f7@linux.ibm.com> (raw)
In-Reply-To: <443ab50f-336b-d559-9788-ace3b34502a1@linux.ibm.com>

On 11/10/20 5:10 PM, Stefan Liebler via Libc-alpha wrote:
> Hi,
> 
> starting with Fedora 33, the xcheck tests posix/bug-ga2-mem and
> resolv/mtrace-tst-leaks2 are failing with "Memory not freed" output of
> mtrace.
> 
> Both tests are activating mtrace and are calling getaddrinfo or
> res_init+gethostbyname for multiple rounds.
> 
> The /etc/nsswitch.conf differs between
> Fedora 32: hosts:      files dns myhostname
> Fedora 33: hosts:      files resolve [!UNAVAIL=return] myhostname dns
> 
> Therefore /lib64/libnss_resolve.so.2 (from systemd) and the dependencies
> libgcc_s.so.1 and libpthread.so.0 are loaded. It seems as those loads
> are recognized in the mtrace output. Does anybody else also get those fails?
> 
> Should we adjust the tests by:
> 
> - calling mtrace() after the first round?
> 
> - running the tests in a container e.g. with a /etc/nsswitch.conf with
> "services: files" and "hosts: files" and a /etc/hosts containing
> www.gnu.org? Those tests would then run with "make check" instead of
> "make xcheck".
> 
> Any ideas?
> 
> Bye,
> Stefan
> 

ping

  reply	other threads:[~2020-11-17  8:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-10 16:10 Stefan Liebler
2020-11-17  8:36 ` Stefan Liebler [this message]
2020-11-17  8:40 ` Florian Weimer
2020-11-17 12:32   ` H.J. Lu
2020-11-19 12:29   ` Stefan Liebler

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=82873473-2595-3934-74db-4570eaacc4f7@linux.ibm.com \
    --to=stli@linux.ibm.com \
    --cc=libc-alpha@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).