|
From: Akos M. <mak...@gm...> - 2011-09-20 09:51:06
|
Hi List, I hope not to disturbing you with my question and isn't that common I should have found the answer somewhere else! Shall I really do some bugreport? Valgrind crashes and give the following output: > > ==27561== Memcheck, a memory error detector > ==27561== Copyright (C) 2002-2010, and GNU GPL'd, by Julian Seward et al. > ==27561== Using Valgrind-3.6.1 and LibVEX; rerun with -h for copyright info > ==27561== Command: ./a.out > ==27561== > --27561-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x2a > > valgrind: m_debuginfo/readdwarf.c:2338 (copy_convert_CfiExpr_tree): Assertion 'srcix >= 0 && srcix < VG_(sizeXA)(srcxa)' failed. > ==27561== at 0x38024575: ??? (in /home/makos/local/lib/valgrind/memcheck-x86-linux) > > sched status: > running_tid=0 > > > 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. Any help is appreciated, because valgrind is completely not useful at this moment for me. Thanks, mAkos |
|
From: Julian S. <js...@ac...> - 2011-09-20 10:01:54
|
I think this has been fixed in the trunk already. See http://valgrind.org/downloads/repository.html J On Tuesday, September 20, 2011, Akos Marton wrote: > Hi List, > > I hope not to disturbing you with my question and isn't that common I > should have found the answer somewhere else! > > Shall I really do some bugreport? > > Valgrind crashes and give the following output: > > ==27561== Memcheck, a memory error detector > > ==27561== Copyright (C) 2002-2010, and GNU GPL'd, by Julian Seward et al. > > ==27561== Using Valgrind-3.6.1 and LibVEX; rerun with -h for copyright > > info ==27561== Command: ./a.out > > ==27561== > > --27561-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x2a > > > > valgrind: m_debuginfo/readdwarf.c:2338 (copy_convert_CfiExpr_tree): > > Assertion 'srcix >= 0 && srcix < VG_(sizeXA)(srcxa)' failed. ==27561== > > at 0x38024575: ??? (in > > /home/makos/local/lib/valgrind/memcheck-x86-linux) > > > > sched status: > > running_tid=0 > > > > 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. > > Any help is appreciated, because valgrind is completely not useful at this > moment for me. > Thanks, mAkos > > --------------------------------------------------------------------------- > --- All the data continuously generated in your IT infrastructure contains > a definitive record of customers, application performance, security > threats, fraudulent activity and more. Splunk takes this data and makes > sense of it. Business sense. IT sense. Common sense. > http://p.sf.net/sfu/splunk-d2dcopy1 > _______________________________________________ > Valgrind-users mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-users |