https://bugs.kde.org/show_bug.cgi?id=358620
Bug ID: 358620
Summary: WARNING: unhandled syscall: 357
Product: valgrind
Version: 3.7.0
Platform: Debian stable
OS: Linux
Status: UNCONFIRMED
Severity: crash
Priority: NOR
Component: memcheck
Assignee: jsew...@acm.org
Reporter: alexander.ress...@gmail.com
I have an ARMv6 Raspberry Pi that I'm compiling and testing a small TCP server
on. I'm using the epoll system call in my c/c++ program. The program runs fine
when I don't use valgrind. However, when I use valgrind, the call to
'epoll_wait' returns -1, which indicates a kernel level error. This doesn't
happen with valgrind and the same program on my typical desktop with an intel
i7 cpu.
See the results of valgrind below.
==2615== Memcheck, a memory error detector
==2615== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
==2615== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info
==2615== Command: ./src/app/bserver
==2615==
--2615-- WARNING: unhandled syscall: 357
--2615-- You may be able to write your own handler.
--2615-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--2615-- Nevertheless we consider this a bug. Please report
--2615-- it at http://valgrind.org/support/bug_reports.html.
--2615-- WARNING: unhandled syscall: 357
--2615-- You may be able to write your own handler.
--2615-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--2615-- Nevertheless we consider this a bug. Please report
--2615-- it at http://valgrind.org/support/bug_reports.html.
disInstr(arm): unhandled instruction: 0xF1010200
cond=15(0xF) 27:20=16(0x10) 4:4=0 3:0=0(0x0)
==2615== valgrind: Unrecognised instruction at address 0x4842588.
==2615== at 0x4842588: ??? (in /usr/lib/arm-linux-gnueabihf/libcofi_rpi.so)
==2615== Your program just tried to execute an instruction that Valgrind
==2615== did not recognise. There are two possible reasons for this.
==2615== 1. Your program has a bug and erroneously jumped to a non-code
==2615== location. If you are running Memcheck and you just saw a
==2615== warning about a bad jump, it's probably your program's fault.
==2615== 2. The instruction is legitimate but Valgrind doesn't handle it,
==2615== i.e. it's Valgrind's fault. If you think this is the case or
==2615== you are not sure, please let us know and we'll try to fix it.
==2615== Either way, Valgrind will now raise a SIGILL signal which will
==2615== probably kill your program.
==2615==
==2615== Process terminating with default action of signal 4 (SIGILL)
==2615== Illegal opcode at address 0x4842588
==2615== at 0x4842588: ??? (in /usr/lib/arm-linux-gnueabihf/libcofi_rpi.so)
==2615==
==2615== HEAP SUMMARY:
==2615== in use at exit: 44,142 bytes in 302 blocks
==2615== total heap usage: 347 allocs, 45 frees, 48,218 bytes allocated
==2615==
==2615== LEAK SUMMARY:
==2615== definitely lost: 0 bytes in 0 blocks
==2615== indirectly lost: 0 bytes in 0 blocks
==2615== possibly lost: 3,060 bytes in 87 blocks
==2615== still reachable: 41,082 bytes in 215 blocks
==2615== suppressed: 0 bytes in 0 blocks
==2615== Rerun with --leak-check=full to see details of leaked memory
==2615==
==2615== For counts of detected and suppressed errors, rerun with: -v
==2615== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
Killed
--
You are receiving this mail because:
You are watching all bug changes.
