Control: found -1 1:3.10.0-4 Another way to reproduce it:
$ mkdir /tmp/bla $ cd /tmp/bla $ valgrind --tool=exp-sgcheck nautilus ==17681== exp-sgcheck, a stack and global array overrun detector ==17681== NOTE: This is an Experimental-Class Valgrind Tool ==17681== Copyright (C) 2003-2013, and GNU GPL'd, by OpenWorks Ltd et al. ==17681== Using Valgrind-3.10.0 and LibVEX; rerun with -h for copyright info ==17681== Command: nautilus ==17681== --17681-- warning: evaluate_Dwarf3_Expr: unhandled DW_OP_ 0x93 --17681-- warning: evaluate_Dwarf3_Expr: unhandled DW_OP_ 0x93 --17681-- warning: evaluate_Dwarf3_Expr: unhandled DW_OP_ 0x93 --17681-- warning: evaluate_Dwarf3_Expr: unhandled DW_OP_ 0x93 --17681-- warning: evaluate_Dwarf3_Expr: unhandled DW_OP_ 0x93 --17681-- warning: evaluate_Dwarf3_Expr: unhandled DW_OP_ 0x93 --17681-- warning: evaluate_Dwarf3_Expr: unhandled DW_OP_ 0x93 --17681-- warning: evaluate_Dwarf3_Expr: unhandled DW_OP_ 0x93 --17681-- warning: evaluate_Dwarf3_Expr: unhandled DW_OP_ 0x93 --17681-- warning: evaluate_Dwarf3_Expr: unhandled DW_OP_ 0x93 --17681-- warning: evaluate_Dwarf3_Expr: unhandled DW_OP_ 0x93 --17681-- warning: evaluate_Dwarf3_Expr: unhandled DW_OP_ 0x93 --17681-- warning: evaluate_Dwarf3_Expr: unhandled DW_OP_ 0x93 --17681-- warning: evaluate_Dwarf3_Expr: unhandled DW_OP_ 0x93 --17681-- warning: evaluate_Dwarf3_Expr: unhandled DW_OP_ 0x93 --17681-- warning: evaluate_Dwarf3_Expr: unhandled DW_OP_ 0x93 exp-sgcheck: sg_main.c:560 (add_blocks_to_StackTree): Assertion '!already_present' failed. host stacktrace: ==17681== at 0x3807BD8F: show_sched_status_wrk (m_libcassert.c:319) ==17681== by 0x3807BE84: report_and_quit (m_libcassert.c:390) ==17681== by 0x3807C006: vgPlain_assert_fail (m_libcassert.c:455) ==17681== by 0x3807225B: add_blocks_to_StackTree (sg_main.c:560) ==17681== by 0x380735BE: shadowStack_new_frame.isra.22 (sg_main.c:1875) ==17681== by 0x806A20AC9: ??? ==17681== by 0x803A62EEF: ??? ==17681== by 0x3806FE6F: ??? (h_main.c:141) ==17681== by 0x8DE4ABA: __nscd_get_mapping (nscd_helper.c:286) sched status: running_tid=1 Thread 1: status = VgTs_Runnable ==17681== at 0x8DE4AF8: __nscd_get_mapping (nscd_helper.c:293) ==17681== by 0x8DE4EDB: __nscd_get_map_ref (nscd_helper.c:443) ==17681== by 0x8DE2E40: __nscd_getai (nscd_getai.c:63) ==17681== by 0x8D9E2C9: gaih_inet (getaddrinfo.c:686) ==17681== by 0x8DA003C: getaddrinfo (getaddrinfo.c:2406) ==17681== by 0xCDFD3FA: ??? (in /usr/lib/x86_64-linux-gnu/libxcb.so.1.1.0) ==17681== by 0xCDFD84C: xcb_connect_to_display_with_auth_info (in /usr/lib/x86_64-linux-gnu/libxcb.so.1.1.0) ==17681== by 0x6DFC0B9: _XConnectXCB (in /usr/lib/x86_64-linux-gnu/libX11.so.6.3.0) ==17681== by 0x6DECDC1: XOpenDisplay (in /usr/lib/x86_64-linux-gnu/libX11.so.6.3.0) ==17681== by 0xE214CCC: ??? (in /usr/lib/x86_64-linux-gnu/libatspi.so.0.0.1) ==17681== by 0xE214FCC: atspi_get_a11y_bus (in /usr/lib/x86_64-linux-gnu/libatspi.so.0.0.1) ==17681== by 0xA75ED05: atk_bridge_adaptor_init (in /usr/lib/x86_64-linux-gnu/libatk-bridge-2.0.so.0.0.0) ==17681== by 0x5727B89: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.1400.5) ==17681== by 0x5892AB0: ??? (in /usr/lib/x86_64-linux-gnu/libgtk-3.so.0.1400.5) ==17681== by 0x7D4B1C8: g_option_context_parse (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4200.1) ==17681== by 0x7D4C0C3: g_option_context_parse_strv (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4200.1) ==17681== by 0x77CFA81: ??? (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.4200.1) ==17681== by 0x77D0176: g_application_run (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.4200.1) ==17681== by 0x429E40: main (nautilus-main.c:103) 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. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
