Attachment 603212 Details for Bug 842659 – Still unusable with valgrind-3.8.0-0.1.TEST1.svn12858.fc18.x86_64

Still unusable with valgrind-3.8.0-0.1.TEST1.svn12858.fc18.x86_64

valglog.1344501701__1049_4843 (text/plain), 4.58 KB, created by Zdenek Kabelac on 2012-08-09 09:20:01 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Zdenek Kabelac

Created: 2012-08-09 09:20:01 UTC

Size: 4.58 KB

patch

obsolete

>==00:00:00:00.000 1050== Memcheck, a memory error detector
>==00:00:00:00.000 1050== Copyright (C) 2002-2012, and GNU GPL'd, by Julian Seward et al.
>==00:00:00:00.000 1050== Using Valgrind-3.8.0-TEST1 and LibVEX; rerun with -h for copyright info
>==00:00:00:00.000 1050== Command: /usr/bin/Xorg.nos :0 -auth /root/.serverauth.1029
>==00:00:00:00.000 1050== Parent PID: 1049
>==00:00:00:00.000 1050== 
>==00:00:00:11.602 1050== Warning: noted but unhandled ioctl 0x6458 with no size/direction hints
>==00:00:00:11.602 1050==    This could cause spurious value errors to appear.
>==00:00:00:11.602 1050==    See README_MISSING_SYSCALL_OR_IOCTL for guidance on writing a proper wrapper.
>### unhandled dwarf2 abbrev form code 0x0
>### unhandled dwarf2 abbrev form code 0x0
>### unhandled dwarf2 abbrev form code 0x2
>### unhandled dwarf2 abbrev form code 0x0
>### unhandled dwarf2 abbrev form code 0x65
>### unhandled dwarf2 abbrev form code 0x0
>### unhandled dwarf2 abbrev form code 0x65
>### unhandled dwarf2 abbrev form code 0x0
>### unhandled dwarf2 abbrev form code 0x0
>### unhandled dwarf2 abbrev form code 0x59
>### unhandled dwarf2 abbrev form code 0x200e9
>### unhandled dwarf2 abbrev form code 0x0
>### unhandled dwarf2 abbrev form code 0x5f
>### unhandled dwarf2 abbrev form code 0x0
>### unhandled dwarf2 abbrev form code 0x5b7
>### unhandled dwarf2 abbrev form code 0x0
>### unhandled dwarf2 abbrev form code 0x388
>### unhandled dwarf2 abbrev form code 0x0
>### unhandled dwarf2 abbrev form code 0x0
>--00:00:00:15.973 1050-- VALGRIND INTERNAL ERROR: Valgrind received a signal 11 (SIGSEGV) - exiting
>--00:00:00:15.973 1050-- si_code=1;  Faulting address: 0x41853B001;  sp: 0x40978c018
>
>valgrind: the 'impossible' happened:
>   Killed by fatal signal
>==00:00:00:15.973 1050==    at 0x380D3680: read_leb128 (readdwarf.c:221)
>==00:00:00:15.973 1050==    by 0x380D3716: read_leb128U (readdwarf.c:247)
>==00:00:00:15.973 1050==    by 0x380D5E2A: vgModuleLocal_read_debuginfo_dwarf3 (readdwarf.c:959)
>==00:00:00:15.973 1050==    by 0x38085FE7: vgModuleLocal_read_elf_debug_info (readelf.c:2678)
>==00:00:00:15.973 1050==    by 0x3807EED5: vgPlain_di_notify_mmap (debuginfo.c:628)
>==00:00:00:15.973 1050==    by 0x380A0E58: vgModuleLocal_generic_PRE_sys_mmap (syswrap-generic.c:2066)
>==00:00:00:15.973 1050==    by 0x380C9C44: vgSysWrap_amd64_linux_sys_mmap_before (syswrap-amd64-linux.c:1012)
>==00:00:00:15.973 1050==    by 0x3809D9A2: vgPlain_client_syscall (syswrap-main.c:1464)
>==00:00:00:15.973 1050==    by 0x3809A6EF: handle_syscall (scheduler.c:1057)
>==00:00:00:15.973 1050==    by 0x3809BC26: vgPlain_scheduler (scheduler.c:1335)
>==00:00:00:15.973 1050==    by 0x380AB729: run_a_thread_NORETURN (syswrap-linux.c:103)
>
>sched status:
>  running_tid=1
>
>Thread 1: status = VgTs_Runnable
>==00:00:00:15.974 1050==    at 0x4017A0A: mmap (syscall-template.S:81)
>==00:00:00:15.974 1050==    by 0x40068DB: _dl_map_object_from_fd (dl-load.c:1344)
>==00:00:00:15.974 1050==    by 0x40083C2: _dl_map_object (dl-load.c:2359)
>==00:00:00:15.974 1050==    by 0x400CCE1: openaux (dl-deps.c:63)
>==00:00:00:15.974 1050==    by 0x400EDC5: _dl_catch_error (dl-error.c:177)
>==00:00:00:15.974 1050==    by 0x400D3C1: _dl_map_object_deps (dl-deps.c:256)
>==00:00:00:15.974 1050==    by 0x4013134: dl_open_worker (dl-open.c:262)
>==00:00:00:15.974 1050==    by 0x400EDC5: _dl_catch_error (dl-error.c:177)
>==00:00:00:15.974 1050==    by 0x4012C0B: _dl_open (dl-open.c:653)
>==00:00:00:15.974 1050==    by 0x5629025: dlopen_doit (dlopen.c:66)
>==00:00:00:15.974 1050==    by 0x400EDC5: _dl_catch_error (dl-error.c:177)
>==00:00:00:15.974 1050==    by 0x562963B: _dlerror_run (dlerror.c:163)
>==00:00:00:15.974 1050==    by 0x56290C0: dlopen@@GLIBC_2.2.5 (dlopen.c:87)
>==00:00:00:15.974 1050==    by 0x7F0F095: glxProbeDriver (glxdricommon.c:225)
>==00:00:00:15.974 1050==    by 0x7F176F4: __glXDRIscreenProbe (glxdri2.c:954)
>==00:00:00:15.974 1050==    by 0x7F0DFC9: GlxExtensionInit (glxext.c:355)
>==00:00:00:15.974 1050==    by 0x4BE128: InitExtensions (in /usr/bin/Xorg.nos)
>==00:00:00:15.974 1050==    by 0x427E9B: ??? (in /usr/bin/Xorg.nos)
>==00:00:00:15.974 1050==    by 0x6E68A04: (below main) (libc-start.c:225)
>
>
>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.
>

Actions: View

Attachments on bug 842659: 599989 | 601750 | 603212