From: David Marchand <david.marchand@redhat.com>
To: Aaron Conole <aconole@redhat.com>,
Rui Ferreira <rui.ferreira1@h-partners.com>
Cc: dev@dpdk.org, bruce.richardson@intel.com,
Michael Santana <maicolgabriel@hotmail.com>,
Patrick Robb <probb@iol.unh.edu>,
Thomas Monjalon <thomas@monjalon.net>,
Konstantin Ananyev <konstantin.ananyev@huawei.com>
Subject: Re: [PATCH v2] ci: check C++ headers with clang
Date: Mon, 7 Jul 2025 16:08:04 +0200 [thread overview]
Message-ID: <CAJFAV8yVE=q6LdSSuy3MzZYxxOvenH3prRZf2dQDL1SyaXFfiA@mail.gmail.com> (raw)
In-Reply-To: <f7tplecqft4.fsf@redhat.com>
On Mon, Jul 7, 2025 at 3:41 PM Aaron Conole <aconole@redhat.com> wrote:
>
> David Marchand <david.marchand@redhat.com> writes:
>
> > If not passing an explicit compiler for C++, meson uses c++ which
> > defaults to /usr/bin/g++ on a Ubuntu system.
> > Explicitly choose which compiler to use for C++.
> >
> > Signed-off-by: David Marchand <david.marchand@redhat.com>
> > ---
> > Changes since v1:
> > - rebased,
> > - moved CXX tweaking in the branch enabling headers check,
> >
>
> Not sure why we got a segfault with this in IOL:
>
> 36/120 DPDK:fast-tests / eal_flags_misc_autotest FAIL 3.78s killed by signal 11 SIGSEGV
Strange segfault indeed.
The logs show:
...
EAL: VFIO support initialized
EAL: invalid parameters for --log-color
EAL: invalid log arguments.
EAL: Unregistering with invalid input parameter
EAL: Memzone is not allocated
This smells like a double free... maybe a race in the cleanup phase.
And then this reminds me of a change we did for v25.07.
d84bf0d9aeb4 ("eal/linux: unregister alarm callback before free")
But I don't see something wrong with this change.
Copying author and reviewer.
> I don't think it is related.
I don't see how my patch on testing headers with C++ could be related :-).
--
David Marchand
prev parent reply other threads:[~2025-07-07 14:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-01 11:31 [PATCH] " David Marchand
2025-07-01 11:37 ` David Marchand
2025-07-03 8:20 ` [PATCH v2] " David Marchand
2025-07-07 13:41 ` Aaron Conole
2025-07-07 14:08 ` David Marchand [this message]
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='CAJFAV8yVE=q6LdSSuy3MzZYxxOvenH3prRZf2dQDL1SyaXFfiA@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=aconole@redhat.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@huawei.com \
--cc=maicolgabriel@hotmail.com \
--cc=probb@iol.unh.edu \
--cc=rui.ferreira1@h-partners.com \
--cc=thomas@monjalon.net \
/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 NNTP newsgroup(s).