Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: Kienan Stewart via lttng-dev <lttng-dev@lists.lttng.org>
To: Norbert Lange <nolange79@gmail.com>,
	lttng-dev <lttng-dev@lists.lttng.org>
Subject: Re: lttng-tools-2.14.0-rc1: ODR violation
Date: Fri, 20 Jun 2025 12:08:05 -0400	[thread overview]
Message-ID: <6ba07571-9594-4097-b1ee-28f07359df86@efficios.com> (raw)
In-Reply-To: <CADYdroPQ-E4JGj=mhQkkRNv4PVgpXuN07fQpg9-r0TifsJpQ5w@mail.gmail.com>

Hi Nortbert,

thanks for the bug report. A change has been merged which addresses this 
warning: 
https://github.com/lttng/lttng-tools/commit/734b1cd20cb8390f9b0f6de9def9d5bccb621197

thanks,
kienan

On 6/17/25 7:00 AM, Norbert Lange via lttng-dev wrote:
> Hello,
> 
> enum communication_state exists twice with already diverging definitions.
> I am not sure if its a functional issue now, but this sound like it
> can cause fun bughunts in the future.
> 
> (enabling lto helps finding that kinda stuff)
> 
> ../../../../src/lib/lttng-ctl/clear.cpp:26:6: warning: type
> 'communication_state' violates the C++ One Definition Rule [-Wodr]
>     26 | enum communication_state {
>        |      ^
> ../../../../src/lib/lttng-ctl/destruction-handle.cpp:25:6: note: an
> enum with different value name is defined in another translation unit
>     25 | enum communication_state {
>        |      ^
> ../../../../src/lib/lttng-ctl/clear.cpp:29:2: note: name
> 'COMMUNICATION_STATE_END' differs from name
> 'COMMUNICATION_STATE_RECEIVE_PAYLOAD' defined in another translation
> unit
>     29 |  COMMUNICATION_STATE_END,
>        |  ^
> ../../../../src/lib/lttng-ctl/destruction-handle.cpp:28:2: note:
> mismatching definition
>     28 |  COMMUNICATION_STATE_RECEIVE_PAYLOAD,
>        |  ^
> 
> Regards, Norbert


      reply	other threads:[~2025-06-20 16:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-17 11:00 Norbert Lange via lttng-dev
2025-06-20 16:08 ` Kienan Stewart via lttng-dev [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=6ba07571-9594-4097-b1ee-28f07359df86@efficios.com \
    --to=lttng-dev@lists.lttng.org \
    --cc=kstewart@efficios.com \
    --cc=nolange79@gmail.com \
    /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