[Bug 573872] Re: valgrind reports with "the 'impossible' happened" message when running
Alessandro Ghedini
ghedo at debian.org
Sat May 12 17:56:58 UTC 2012
This should have already been fixed (the provided test works fine too).
** Changed in: valgrind (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to valgrind in Ubuntu.
https://bugs.launchpad.net/bugs/573872
Title:
valgrind reports with "the 'impossible' happened" message when running
Status in “valgrind” package in Ubuntu:
Fix Released
Bug description:
Binary package hint: valgrind
I am using valgrind to profile memory usage in my program that uses v8 javascript engine.
It looks like some expectations failed within a library that valgrind uses, an output is as follows:
==5285== Massif, a heap profiler
==5285== Copyright (C) 2003-2009, and GNU GPL'd, by Nicholas Nethercote
==5285== Using Valgrind-3.6.0.SVN-Debian and LibVEX; rerun with -h for copyright info
==5285== Command: ./bi-eng
==5285==
./bi-eng (1): embedded js engine
vex: priv/guest_amd64_toIR.c:14674 (disInstr_AMD64_WRK): Assertion `sz == 2 || sz == 4' failed.
vex storage: T total 343595872 bytes allocated
vex storage: P total 816 bytes allocated
valgrind: the 'impossible' happened:
LibVEX called failure_exit().
==5285== at 0x38005E17: report_and_quit (m_libcassert.c:191)
==5285== by 0x38005E7E: panic (m_libcassert.c:275)
==5285== by 0x38005ED8: vgPlain_core_panic_at (m_libcassert.c:280)
==5285== by 0x38005EEA: vgPlain_core_panic (m_libcassert.c:285)
==5285== by 0x3801C9C2: failure_exit (m_translate.c:674)
==5285== by 0x38094E98: vex_assert_fail (main_util.c:230)
==5285== by 0x380F8181: disInstr_AMD64_WRK (guest_amd64_toIR.c:14674)
==5285== by 0x380FF345: disInstr_AMD64 (guest_amd64_toIR.c:16238)
==5285== by 0x380A38F7: bb_to_IR (guest_generic_bb_to_IR.c:241)
==5285== by 0x3809367E: LibVEX_Translate (main_main.c:453)
==5285== by 0x3801A62B: vgPlain_translate (m_translate.c:1518)
==5285== by 0x3803DE48: vgPlain_scheduler (scheduler.c:857)
==5285== by 0x380671C4: run_a_thread_NORETURN (syswrap-linux.c:91)
sched status:
running_tid=1
Thread 1: status = VgTs_Runnable
==5285== at 0x9F9AEFB: ???
==5285== by 0x9F99AC8: ???
==5285== by 0x9F997EA: ???
==5285== by 0x9F96B97: ???
==5285== by 0x9F768EA: ???
==5285== by 0x42F9E2: v8::internal::Invoke(bool, v8::internal::Handle<v8::internal::JSFunction>, v8::internal::Handle<v8::internal::Object>, int, v8::internal::Object***, bool*) (in /home/sasha/proj/qtcgen/min/v8use/bin/debug/bi-eng)
==5285== by 0x42FDD8: v8::internal::Execution::Call(v8::internal::Handle<v8::internal::JSFunction>, v8::internal::Handle<v8::internal::Object>, int, v8::internal::Object***, bool*) (in /home/sasha/proj/qtcgen/min/v8use/bin/debug/bi-eng)
==5285== by 0x40B149: v8::Script::Run() (in /home/sasha/proj/qtcgen/min/v8use/bin/debug/bi-eng)
==5285== by 0x402C74: sample_simple_embed() (main.cpp:27)
==5285== by 0x402DA1: main (main.cpp:40)
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.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: valgrind 1:3.6.0~svn20100212-0ubuntu5
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic x86_64
Architecture: amd64
Date: Sun May 2 22:15:42 2010
ProcEnviron:
PATH=(custom, user)
LANG=en_US.utf8
SHELL=/bin/bash
SourcePackage: valgrind
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/valgrind/+bug/573872/+subscriptions
More information about the foundations-bugs
mailing list