Bug 274089 - exp-ptrcheck: the 'impossible' happened: unhandled syscall (sysno == 208)
Summary: exp-ptrcheck: the 'impossible' happened: unhandled syscall (sysno == 208)
Status: RESOLVED FIXED
Alias: None
Product: valgrind
Classification: Developer tools
Component: sgcheck (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Julian Seward
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-25 10:41 UTC by R
Modified: 2012-08-10 14:04 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description R 2011-05-25 10:41:32 UTC
Version:           unspecified
OS:                Linux



Reproducible: Sometimes

Steps to Reproduce:
valgrind --trace-children=yes --read-var-info=yes --num-callers=30  --suppressions=s1.supp --suppressions=s2.supp  --tool=exp-ptrcheck  --log-file=host%p.log XXXmyprogramXXX

Actual Results:  
==2805== exp-ptrcheck, a heap, stack and global array overrun detector
==2805== NOTE: This is an Experimental-Class Valgrind Tool
==2805== Copyright (C) 2003-2010, and GNU GPL'd, by OpenWorks Ltd et al.
==2805== Using Valgrind-3.6.1 and LibVEX; rerun with -h for copyright info
==2805== Command: XXXmyprgramXXX
==2805== Parent PID: 2804
==2805== 
sysno == 208
exp-ptrcheck: the 'impossible' happened:
   unhandled syscall
==2805==    at 0x38014ACD: report_and_quit (m_libcassert.c:193)
==2805==    by 0x38014B26: panic (m_libcassert.c:277)
==2805==    by 0x38014B5F: vgPlain_tool_panic (m_libcassert.c:292)
==2805==    by 0x3800287A: h_post_syscall (h_main.c:2600)
==2805==    by 0x3805836C: vgPlain_post_syscall (syswrap-main.c:1729)
==2805==    by 0x38058FB3: vgPlain_client_syscall (syswrap-main.c:1627)
==2805==    by 0x38055262: handle_syscall (scheduler.c:895)
==2805==    by 0x3805639E: vgPlain_scheduler (scheduler.c:1091)
==2805==    by 0x38084344: run_a_thread_NORETURN (syswrap-linux.c:94)
==2805==    by 0x38084602: vgModuleLocal_start_thread_NORETURN (syswrap-linux.c:225)
==2805==    by 0x38087648: ??? (in /usr/local/lib/valgrind/exp-ptrcheck-x86-linux)

sched status:
  running_tid=2

Thread 1: status = VgTs_WaitSys
==2805==    at 0x4000832: ??? (in /lib/ld-2.11.1.so)
==2805==    by 0x441565B: seteuid (in /lib/tls/i686/cmov/libc-2.11.1.so)
==2805==    by 0x8078A2B: DwCommIOimplVendor::OpenListen() (dwcommio.cpp:264)
==2805==    by 0x80787EB: DwCommIOimplVendor::DwCommIOimplVendor(unsigned char, char const*) (dwcommio.cpp:227)
==2805==    by 0x807A009: DwCommIOimpl::DwCommIOimpl(unsigned char, char const*) (dwcommio.cpp:792)
==2805==    by 0x8079A01: DwCommIO::DwCommIO(bool) (dwcommio.cpp:878)
==2805==    by 0x807A0BE: DwCommDTLIO::DwCommDTLIO(bool) (dwcommdtlio.cpp:7)
==2805==    by 0x8060E42: DwAppHostQt::GuiCreate() (dwapphostqt.cpp:423)
==2805==    by 0x8060423: DwAppHostQt::Open(bool) (dwapphostqt.cpp:158)
==2805==    by 0x805F79C: main (dwhost.cpp:579)

Thread 2: status = VgTs_Runnable
==2805==    at 0x4000832: ??? (in /lib/ld-2.11.1.so)
==2805==    by 0x40A536F: ??? (in /lib/tls/i686/cmov/libpthread-2.11.1.so)
==2805==    by 0x805ED23: exit_thread_run(void*) (dwhost.cpp:133)
==2805==    by 0x409C96D: start_thread (in /lib/tls/i686/cmov/libpthread-2.11.1.so)
==2805==    by 0x441CA4D: clone (in /lib/tls/i686/cmov/libc-2.11.1.so)


Note: see also the FAQ in the source distribution.
It contains workarounds to several common problems.
In particular, if Valgrind aborted or crashed after
identifying problems in your program, there's a good chance
that fixing those problems will prevent Valgrind aborting or
crashing, especially if it happened in m_mallocfree.c.

If that doesn't help, please report this bug to: www.valgrind.org

In the bug report, send all the above text, the valgrind
version, and what OS and version you are using.  Thanks.


OS: Ubuntu 10.04 desktop 32bit
Valgrind: 3.6.1
Comment 1 Tom Hughes 2011-08-10 10:09:20 UTC
This is no longer an issue in the current code as exp-ptrcheck has been simplified and renamed as exp-sgcheck and no longer needs to monitor system calls. As a result the code containing this assertion no longer exists.