|
From: Carl E. L. <ce...@us...> - 2015-04-21 15:32:01
|
On Tue, 2015-04-21 at 12:20 +0000,
val...@li... wrote:
> Message: 4
> Date: Tue, 21 Apr 2015 10:58:00 +0200
> From: Thomas Huth <th...@re...>
> Subject: [Valgrind-developers] unhandled ppc64be-linux syscall: 175
> To: val...@li...
> Message-ID: <20150421105800.7ef1bb82@thh440s>
> Content-Type: text/plain; charset=US-ASCII
>
>
> Hi all!
>
> While trying to run qemu with valgrind on a ppc64 host, I've
> encountered the following warning message from valgrind:
>
> --11641-- WARNING: unhandled ppc64be-linux syscall: 175
>
> valgrind then stops execution, so this was rather an error message
> than
> a warning message, I guess ;-)
>
> The following patch seems to fix this issue for me, however since I am
> not very experienced with valgrind yet, could somebody please have a
> closer look whether this is the right way to deal with this missing
> syscall?
>
> Thanks,
> Thomas
> diff -u a/coregrind/m_syswrap/syswrap-ppc64-linux.c
> b/coregrind/m_syswrap/syswrap-ppc64-linux.c
> --- a/coregrind/m_syswrap/syswrap-ppc64-linux.c 2015-04-21
> 10:51:45.450216797 +0200
> +++ b/coregrind/m_syswrap/syswrap-ppc64-linux.c 2015-04-21
> 10:27:34.916665631 +0200
> @@ -988,7 +988,7 @@
> LINXY(__NR_rt_sigaction, sys_rt_sigaction), // 173
> LINXY(__NR_rt_sigprocmask, sys_rt_sigprocmask), // 174
>
> -// _____(__NR_rt_sigpending, sys_rt_sigpending), // 175
> + LINXY(__NR_rt_sigpending, sys_rt_sigpending), // 175
> LINXY(__NR_rt_sigtimedwait, sys_rt_sigtimedwait), // 176
> LINXY(__NR_rt_sigqueueinfo, sys_rt_sigqueueinfo), // 177
> LINX_(__NR_rt_sigsuspend, sys_rt_sigsuspend), // 178
Thomas:
I will look into this with you. Can you send me directly
(ce...@us...) your test case. I will see about testing your patch
and getting a fix committed. Thanks.
Carl Love
|