Re: [Valgrind-users] compat_ioctl cmd does not match even if it shows same value

Hi John, Valgrind version: valgrind-3.14.0 compat_ioctl prototype: /* File operations core */ struct file_operations mgr_fops = { owner: THIS_MODULE, open: mgr_open_common, FILE_OPS_IOCTL(mgr_ioctl_common), #ifdef CONFIG_COMPAT compat_ioctl: mgr_compat_

Re: [Valgrind-users] compat_ioctl cmd does not match even if it shows same value

I have a 32 bit application (user space) which communicate with a kernel module through compat_ioctl(). My system is # uname -a Linux chassis1-board1-port5 3.10 #1 SMP Fri Apr 24 02:31:48 PDT 2020 mips64 GNU/Linux Which version of valgrind? The source code of valgrind: commit 24b247aec5

[Valgrind-users] compat_ioctl cmd does not match even if it shows same value

Hi, I have a 32 bit application (user space) which communicate with a kernel module through compat_ioctl(). My system is # uname -a Linux chassis1-board1-port5 3.10 #1 SMP Fri Apr 24 02:31:48 PDT 2020 mips64 GNU/Linux Ioctl function is following: long mgr_compat_ioctl(struct file *pFile, unsigne

Re: [Valgrind-users] compat_ioctl cmd does not match even if it shows same value

(openLink - cmd) shows zero still if check fails. Note: this is happening only under valgrind! Regards, Mano, IxNetwork [Keysight-signature-block-5] From: Manomugdha Biswas Sent: Saturday, August 15, 2020 6:38 PM To: valgrind-users@lists.sourceforge.net Subject: compat_i

Re: [Valgrind-users] Use of valgrind with microthreading

On Fri, 2020-08-14 at 19:16 +0200, Mark Wielaard wrote: > Hi Shachar, > > On Fri, Aug 14, 2020 at 06:35:14PM +0300, Shachar Shemesh wrote: > > I am writing my own C++ microthreading library. At the very first switch, I > > get the following message from Valgrind: > > > > ==15122== Warning: client