linux-trace-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yordan Karadzhov <ykaradzhov@vmware.com>
To: Alan Mikhak <alanmikhak@gmail.com>,
	"linux-trace-devel@vger.kernel.org" 
	<linux-trace-devel@vger.kernel.org>,
	"rostedt@goodmis.org" <rostedt@goodmis.org>
Cc: Alan Mikhak <amikhak@wirelessfabric.com>
Subject: Re: [PATCH] Fix compiler error in KsSession.cpp on Raspberry Pi 3
Date: Wed, 12 Jun 2019 07:34:35 +0000	[thread overview]
Message-ID: <b0108c01-00f4-fc5e-7fef-03e6984f361e@vmware.com> (raw)
In-Reply-To: <20190612035902.16366-1-amikhak@wirelessfabric.com>



On 12.06.19 г. 6:59 ч., Alan Mikhak wrote:
> Fix compiler error at KsSession.cpp:457:30 on Raspberry Pi 3
> 
> Fix by changing the type of local variable 'pos' from uint64_t to
> size_t in KsSession::loadDualMarker().
> 
> KsSession.cpp:457:30: error: no matching function for call to
> ‘KsSession::_getMarker(const char [6], uint64_t*)’
>    if (_getMarker("markA", &pos)) {
>                                ^
> In file included from KsSession.cpp:14:0:
> KsSession.hpp:97:7: note: candidate:
>   bool KsSession::_getMarker(const char*, size_t*)
>    bool _getMarker(const char* name, size_t *pos);
>         ^~~~~~~~~~
> KsSession.hpp:97:7: note:   no known conversion for
> argument 2 from ‘uint64_t* {aka long long unsigned int*}’
> to ‘size_t* {aka unsigned int*}’
> 
> Signed-off-by: Alan Mikhak <amikhak@wirelessfabric.com>
> ---
>   kernel-shark/src/KsSession.cpp | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/kernel-shark/src/KsSession.cpp b/kernel-shark/src/KsSession.cpp
> index 9d86776..a581bbf 100644
> --- a/kernel-shark/src/KsSession.cpp
> +++ b/kernel-shark/src/KsSession.cpp
> @@ -450,7 +450,7 @@ void KsSession::saveDualMarker(KsDualMarkerSM *dm)
>    */
>   void KsSession::loadDualMarker(KsDualMarkerSM *dm, KsTraceGraph *graphs)
>   {
> -	uint64_t pos;
> +	size_t pos;
>   
>   	dm->reset();
>   	dm->setState(DualMarkerState::A);
> 


Hi Alan,
Thanks a lot for this fix!

Reviewed-by: Yordan Karadzhov <ykaradzhov@vmware.com>

I am really curious to know how does KernelShark look and feel on 
Raspberry Pi. Would you shared with us your impressions.
Honestly, I will be surprised if everything works fine ;)

Cheers,
Yordan

  reply	other threads:[~2019-06-12  7:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-12  3:59 [PATCH] Fix compiler error in KsSession.cpp on Raspberry Pi 3 Alan Mikhak
2019-06-12  7:34 ` Yordan Karadzhov [this message]
2019-06-12 12:12   ` Steven Rostedt
2019-06-12 15:31     ` Alan Mikhak
2019-06-12 15:53       ` Steven Rostedt
2019-06-12 15:22   ` Alan Mikhak
2019-06-14  4:40     ` Alan Mikhak
2019-06-12  8:17 ` Yordan Karadzhov
2019-06-12 12:11   ` 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=b0108c01-00f4-fc5e-7fef-03e6984f361e@vmware.com \
    --to=ykaradzhov@vmware.com \
    --cc=alanmikhak@gmail.com \
    --cc=amikhak@wirelessfabric.com \
    --cc=linux-trace-devel@vger.kernel.org \
    --cc=rostedt@goodmis.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 NNTP newsgroup(s).