From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
linux-trace-devel@vger.kernel.org,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Subject: Re: [PATCH 1/2] parse-events: deref pointer for proper sizeof()
Date: Tue, 6 Aug 2019 14:14:18 +0900 [thread overview]
Message-ID: <20190806051418.GB851@jagdpanzerIV> (raw)
In-Reply-To: <20190805232103.04c6ad28@oasis.local.home>
On (08/05/19 23:21), Steven Rostedt wrote:
> On Mon, 5 Aug 2019 19:26:45 +0900
> Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com> wrote:
>
> > Signed-off-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
> > ---
>
> Hi Sergey,
>
> Thanks for sending these!
Hi Steven,
I just realised that the patches are against v1.1.1, not the master
branch. Let me know if it's not OK.
I've some issues building v1.1.1.
swig -Wall -python -noproxy ctracecmd.i
parse-events.h:676: Error: Syntax error in input(3).
Which is, probably, this 'bool' variable of type filter_arg_boolean
struct filter_arg {
enum filter_arg_type type;
union {
struct filter_arg_boolean bool; <<<< 676
struct filter_arg_field field;
struct filter_arg_value value;
struct filter_arg_op op;
struct filter_arg_exp exp;
struct filter_arg_num num;
struct filter_arg_str str;
};
};
Is this a known problem?
-ss
next prev parent reply other threads:[~2019-08-06 5:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-05 10:26 [PATCH 1/2] parse-events: deref pointer for proper sizeof() Sergey Senozhatsky
2019-08-05 10:26 ` [PATCH 2/2] " Sergey Senozhatsky
2019-08-06 3:21 ` [PATCH 1/2] " Steven Rostedt
2019-08-06 5:14 ` Sergey Senozhatsky [this message]
2019-08-06 5:41 ` Sergey Senozhatsky
2019-08-06 6:07 ` Sergey Senozhatsky
2019-08-06 12:50 ` Steven Rostedt
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=20190806051418.GB851@jagdpanzerIV \
--to=sergey.senozhatsky.work@gmail.com \
--cc=linux-trace-devel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky@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;
as well as URLs for NNTP newsgroup(s).