On Mar 30, 2011, at 4:20 AM, Julian Seward wrote:
> On Wednesday, March 30, 2011, Adam Seering wrote:
>> I'll take a look. If it's easy enough that I can figure it out, I'll make
>> the change myself; otherwise I'll file an appropriate bug report.
>
> It's trivial -- look at the code. The only
On Wednesday, March 30, 2011, Adam Seering wrote:
> I'll take a look. If it's easy enough that I can figure it out, I'll make
> the change myself; otherwise I'll file an appropriate bug report.
It's trivial -- look at the code. The only distinction you need
to make is whether or not the returned
On Mar 29, 2011, at 11:11 PM, John Reiser wrote:
>> Thanks for the reply. ... I'm not sure what 2.6.22-rc1 has to do with this
>> syscall? Or what, if anything, I can do?
>
> The eventfd2 syscall was added to the Linux kernel in mid 2007, for Linux
> 26.22,
> but exp-ptrcheck has no handler f
> Thanks for the reply. ... I'm not sure what 2.6.22-rc1 has to do with this
> syscall? Or what, if anything, I can do?
The eventfd2 syscall was added to the Linux kernel in mid 2007, for Linux
2.6.22,
but exp-ptrcheck has no handler for it today. Section 11.6, Limitations, of the
valgrind man
> I'm trying to debug an app on Ubuntu 10.10 x86_64. When I open it in
> exp-ptrcheck, I get the following error:
>
> sysno == 290
> exp-ptrcheck: the 'impossible' happened:
> unhandled syscall
-/usr/include/asm/unistd_64.h
#define __NR_eventfd2 290
-
Hi,
I'm trying to debug an app on Ubuntu 10.10 x86_64. When I open it in
exp-ptrcheck, I get the following error:
sysno == 290
exp-ptrcheck: the 'impossible' happened:
unhandled syscall
==8235==at 0x3801303F: report_and_quit (m_libcassert.c:191)
==8235==by 0x38013138: panic (m_
