On Mon, Mar 24, 2014 at 3:15 PM, Tom Hughes wrote:
> On 24/03/14 09:37, Subhashish Pradhan wrote:
>
>> 1 - It was mentioned "it may well be that no memory is read/written,
>> but you'd have to look at the kernel and see what that ioctl does to
>> be sure."
cally I'd need to implement
syswrap-platform.c, and maybe syscall-platform.S, am I right?
5 - What's the speciality about the syscall-platform.S - why's it so
"magical" as referred in syswrap-main.c?
Regards,
Subhashish Pradhan
On Mon, Mar 24, 2014 at 2:10 PM, Tom Hughes wr
nderstand the 0x5309 operation code
context as explained in this post on this mailing list below:
<http://valgrind.10908.n7.nabble.com/noted-but-unhandled-ioctl-0xae03-with-no-size-direction-hints-tp38957p38959.html>
How can we use that opcode to wri
Hello again!
I asked around and found that it was another name for syscalls in gnumach.
Thanks again!
Regards,
Subhashish
On Sat, Jan 11, 2014 at 4:00 AM, Tom Hughes wrote:
> On 10/01/14 21:47, Subhashish Pradhan wrote:
>
> One last query: Are the kernel traps also implemented
Hello again,
One last query: Are the kernel traps also implemented there in coregrind or
somewhere else?
May I have the location like that for syscalls?
Regards,
Subhashish
On Fri, Jan 10, 2014 at 5:06 PM, Subhashish Pradhan wrote:
> Thanks so much! I googled a lot but couldn't eve
:
> On Thu, 2014-01-09 at 19:40 +0530, Subhashish Pradhan wrote:
> > Hello!
> >
> >
> > I have some theoretical queries. What does "teaching valgrind some
> > syscalls" mean?
> >
> >
> > What are the read and write primitives of valgrind a
Hello!
I have some theoretical queries. What does "teaching valgrind some
syscalls" mean?
What are the read and write primitives of valgrind and where are they
handled?
Forgive me for being such a newbie, in advance.
Regards,
Subhashish
P.S. - Which documentation should provide the essential u
