From: Michael Jeanson via lttng-dev <lttng-dev@lists.lttng.org>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: lttng-dev <lttng-dev@lists.lttng.org>
Subject: Re: [lttng-dev] [PATCH] Fix: tracepoint.h: define SDT_USE_VARIADIC in pkg-config CFLAGS
Date: Mon, 29 Jun 2020 12:36:57 -0400 (EDT) [thread overview]
Message-ID: <1076462414.15458.1593448617213.JavaMail.zimbra@efficios.com> (raw)
Message-ID: <20200629163657.quyta8bpIBoTlkFpJlbLCetHN2ysbq6zbrsXOrT00Po@z> (raw)
In-Reply-To: <20200629162600.GA54368@stefanha-x1.localdomain>
----- On 29 Jun, 2020, at 12:26, Stefan Hajnoczi stefanha@redhat.com wrote:
> On Fri, Jun 26, 2020 at 05:02:00PM -0400, Michael Jeanson wrote:
>> I proposed a patch here[1] that addresses this problem in a generic way by
>> duplicating the macro and namespacing it under LTTNG_. Honestly this is more
>> of an sdt bug, the STAP_PROBEV should be in it's own include guard outside
>> of _SYS_SDT_H or in it's own header file but we have to work with what's there.
>>
>> Can you have a look at the patch and confirm that it fixes your problem?
>
> Great, glad there is already a fix under review.
>
> When I try out the patch the application does not compile. The error
> messages are the same as without the patch because _LTTNG_SDT_PROBE() is
> not defined. Was that supposed to be _SDT_PROBE() instead?
>
> The application compiles successfully after replacing _LTTNG_SDT_PROBE()
> with _SDT_PROBE().
>
> Stefan
Yes indeed, I reworked the patch after testing it and didn't catch this, I've
just pushed an updated patch. Thanks for testing it and catching this.
Cheers,
Michael
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
next prev parent reply other threads:[~2020-06-29 16:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-24 16:09 [PATCH] Fix: tracepoint.h: define SDT_USE_VARIADIC in pkg-config CFLAGS Stefan Hajnoczi via lttng-dev
2020-06-24 16:09 ` [lttng-dev] " Stefan Hajnoczi via lttng-dev
2020-06-26 21:02 ` Michael Jeanson via lttng-dev
2020-06-26 21:02 ` [lttng-dev] " Michael Jeanson via lttng-dev
2020-06-29 16:26 ` Stefan Hajnoczi via lttng-dev
2020-06-29 16:26 ` [lttng-dev] " Stefan Hajnoczi via lttng-dev
2020-06-29 16:36 ` Michael Jeanson via lttng-dev [this message]
2020-06-29 16:36 ` Michael Jeanson via lttng-dev
2020-06-30 9:05 ` Stefan Hajnoczi via lttng-dev
2020-06-30 9:05 ` [lttng-dev] " Stefan Hajnoczi via lttng-dev
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=1076462414.15458.1593448617213.JavaMail.zimbra@efficios.com \
--to=lttng-dev@lists.lttng.org \
--cc=mjeanson@efficios.com \
--cc=stefanha@redhat.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;
as well as URLs for NNTP newsgroup(s).