|
From: Alasdair F. <ala...@sp...> - 2005-10-20 09:12:17
|
When I run valgrind on some code here, I get the following before
Valgrind exits. I guess this is something to do with an illegal memory
access, but it runs fine in gdb and without any form of debugger, so I'm
at a slight loss. Am I on the right thread, or way of target? Any help /
suggestions would be appreciated!
Valgrind 3.0.1, Redhat 9 / i686
Thanks,
Alasdair
valgrind: dwarf.c:411 (read_dwarf2_lineblock): Assertion 'noLargerThan >
0' failed.
==4117== at 0xB0016E14: panic (m_libcassert.c:175)
==4117== by 0xB0016E13: vgPlain_assert_fail (m_libcassert.c:169)
==4117== by 0xB002F734: read_dwarf2_lineblock (dwarf.c:523)
==4117== by 0xB002FE7D: vgModuleLocal_read_debuginfo_dwarf2 (dwarf.c:953)
==4117== by 0xB002BF3A: read_lib_symbols (symtab.c:1626)
==4117== by 0xB002C09E: vgPlain_read_seg_symbols (symtab.c:1680)
==4117== by 0xB00411B3: vgPlain_map_file_segment (aspacemgr.c:816)
==4117== by 0xB0041348: vgPlain_map_fd_segment (aspacemgr.c:862)
==4117== by 0xB0042954: vgModuleLocal_mmap_segment
(syswrap-generic.c:148)
==4117== by 0xB005A4BB: vgSysWrap_x86_linux_old_mmap_before
(syswrap-x86-linux.c:1538)
==4117== by 0xB005BDD3: vgPlain_client_syscall (syswrap-main.c:622)
==4117== by 0xB003E453: handle_syscall (scheduler.c:589)
==4117== by 0xB003E76B: vgPlain_scheduler (scheduler.c:688)
==4117== by 0xB005C97A: vgModuleLocal_thread_wrapper (syswrap-linux.c:80)
==4117== by 0xB0057AC8: run_a_thread_NORETURN (syswrap-x86-linux.c:150)
sched status:
running_tid=1
Thread 1: status = VgTs_Runnable
==4117== at 0x1B8F50BD: mmap (in /lib/ld-2.3.2.so)
==4117== by 0x1B8E868A: _dl_map_object (in /lib/ld-2.3.2.so)
==4117== by 0x1B8EFC27: openaux (in /lib/ld-2.3.2.so)
==4117== by 0x1B8F0265: _dl_catch_error (in /lib/ld-2.3.2.so)
==4117== by 0x1B8EF0AD: _dl_map_object_deps (in /lib/ld-2.3.2.so)
==4117== by 0x1B8E539D: dl_main (in /lib/ld-2.3.2.so)
==4117== by 0x1B8F2EAE: _dl_sysdep_start (in /lib/ld-2.3.2.so)
==4117== by 0x1B8E4F22: _dl_start (in /lib/ld-2.3.2.so)
==4117== by 0x1B8E4BE6: (within /lib/ld-2.3.2.so)
--
------------------------------------------------------------------------
Alasdair Ferro SpiraTech Ltd,
Product Conformance Engineer Carrington Business Park,
mailto:ala...@sp... Manchester,
Work: +44 (0)161 776 4582 M31 4ZU, U.K.
http://www.spiratech.com
------------------------------------------------------------------------
This email and any files transmitted with it are confidential and
may be legally privileged. It is intended solely for the use of the
individual or entity to whom it is addressed. If you have received
this in error, please contact the sender and delete the material
immediately. Whilst this email has been swept for viruses, you
should carry out your own virus check before opening any
attachment. SpiraTech Ltd accepts no liability for any loss or
damage which may be caused by software viruses or interception
or interruption of this email.
|
|
From: Tom H. <to...@co...> - 2005-10-20 09:45:51
|
In message <435...@sp...>
Alasdair Ferro <ala...@sp...> wrote:
> When I run valgrind on some code here, I get the following before
> Valgrind exits. I guess this is something to do with an illegal memory
> access, but it runs fine in gdb and without any form of debugger, so
> I'm at a slight loss. Am I on the right thread, or way of target? Any
> help / suggestions would be appreciated!
There's no illegal memory access involved - this is an assertion
firing in valgrind. In other words some assumption that is being
made in the DWARF reader is not valid for some reason.
> valgrind: dwarf.c:411 (read_dwarf2_lineblock): Assertion 'noLargerThan
>> 0' failed.
> ==4117== at 0xB0016E14: panic (m_libcassert.c:175)
> ==4117== by 0xB0016E13: vgPlain_assert_fail (m_libcassert.c:169)
> ==4117== by 0xB002F734: read_dwarf2_lineblock (dwarf.c:523)
> ==4117== by 0xB002FE7D: vgModuleLocal_read_debuginfo_dwarf2 (dwarf.c:953)
> ==4117== by 0xB002BF3A: read_lib_symbols (symtab.c:1626)
> ==4117== by 0xB002C09E: vgPlain_read_seg_symbols (symtab.c:1680)
> ==4117== by 0xB00411B3: vgPlain_map_file_segment (aspacemgr.c:816)
> ==4117== by 0xB0041348: vgPlain_map_fd_segment (aspacemgr.c:862)
> ==4117== by 0xB0042954: vgModuleLocal_mmap_segment
> (syswrap-generic.c:148)
> ==4117== by 0xB005A4BB: vgSysWrap_x86_linux_old_mmap_before
> (syswrap-x86-linux.c:1538)
> ==4117== by 0xB005BDD3: vgPlain_client_syscall (syswrap-main.c:622)
> ==4117== by 0xB003E453: handle_syscall (scheduler.c:589)
> ==4117== by 0xB003E76B: vgPlain_scheduler (scheduler.c:688)
> ==4117== by 0xB005C97A: vgModuleLocal_thread_wrapper (syswrap-linux.c:80)
> ==4117== by 0xB0057AC8: run_a_thread_NORETURN (syswrap-x86-linux.c:150)
First things first, please open a bug for this so that it can be
properly tracked.
Second, can you change line 949 of coregrind/m_debuginfo/dwarf.c so
that it reads "if (1)" instead of "if (0)" then run again with -v and
add the output to the bug.
Thanks,
Tom
--
Tom Hughes (to...@co...)
http://www.compton.nu/
|
|
From: Alasdair F. <ala...@sp...> - 2005-10-20 10:42:34
|
Done: http://bugs.kde.org/show_bug.cgi?id=114757 As a word of warning, I can't give you an example, as this is proprietary code :-( But I can experiment for you :-) Thanks for the quick reply. Alasdair >>When I run valgrind on some code here, I get the following before >>Valgrind exits. I guess this is something to do with an illegal memory >>access, but it runs fine in gdb and without any form of debugger, so >>I'm at a slight loss. Am I on the right thread, or way of target? Any >>help / suggestions would be appreciated! >> >> >There's no illegal memory access involved - this is an assertion >firing in valgrind. In other words some assumption that is being >made in the DWARF reader is not valid for some reason. > > >>valgrind: dwarf.c:411 (read_dwarf2_lineblock): Assertion 'noLargerThan > 0' failed. >> >> >>==4117== at 0xB0016E14: panic (m_libcassert.c:175) >>==4117== by 0xB0016E13: vgPlain_assert_fail (m_libcassert.c:169) >>==4117== by 0xB002F734: read_dwarf2_lineblock (dwarf.c:523) >>==4117== by 0xB002FE7D: vgModuleLocal_read_debuginfo_dwarf2 (dwarf.c:953) >>==4117== by 0xB002BF3A: read_lib_symbols (symtab.c:1626) >>==4117== by 0xB002C09E: vgPlain_read_seg_symbols (symtab.c:1680) >>==4117== by 0xB00411B3: vgPlain_map_file_segment (aspacemgr.c:816) >>==4117== by 0xB0041348: vgPlain_map_fd_segment (aspacemgr.c:862) >>==4117== by 0xB0042954: vgModuleLocal_mmap_segment >>(syswrap-generic.c:148) >>==4117== by 0xB005A4BB: vgSysWrap_x86_linux_old_mmap_before >>(syswrap-x86-linux.c:1538) >>==4117== by 0xB005BDD3: vgPlain_client_syscall (syswrap-main.c:622) >>==4117== by 0xB003E453: handle_syscall (scheduler.c:589) >>==4117== by 0xB003E76B: vgPlain_scheduler (scheduler.c:688) >>==4117== by 0xB005C97A: vgModuleLocal_thread_wrapper (syswrap-linux.c:80) >>==4117== by 0xB0057AC8: run_a_thread_NORETURN (syswrap-x86-linux.c:150) >> >> >First things first, please open a bug for this so that it can be >properly tracked. > >Second, can you change line 949 of coregrind/m_debuginfo/dwarf.c so >that it reads "if (1)" instead of "if (0)" then run again with -v and >add the output to the bug. > > -- ------------------------------------------------------------------------ Alasdair Ferro SpiraTech Ltd, Product Conformance Engineer Carrington Business Park, mailto:ala...@sp... Manchester, Work: +44 (0)161 776 4582 M31 4ZU, U.K. http://www.spiratech.com ------------------------------------------------------------------------ This email and any files transmitted with it are confidential and may be legally privileged. It is intended solely for the use of the individual or entity to whom it is addressed. If you have received this in error, please contact the sender and delete the material immediately. Whilst this email has been swept for viruses, you should carry out your own virus check before opening any attachment. SpiraTech Ltd accepts no liability for any loss or damage which may be caused by software viruses or interception or interruption of this email. |