|
From: Tom H. <to...@co...> - 2007-06-02 13:08:08
|
In message <200...@en...>
Diego 'Flameeyes' Pettenò <fla...@gm...> wrote:
> On Sat, 2 Jun 2007 10:42:36 +0100
> Julian Seward <js...@ac...> wrote:
>
> > Sure, this could be pushed into 3.2.4 if it does not cause any big
> > complications.
>
> I've jsut tried backporting that patch to valgrind 3.2.3, but the
> result is the same as the previous valgrind (built against 2.5) running
> on 2.6:
>
> valgrind: the 'impossible' happened:
> repeated section!
>
> ==9029== at 0x38018B2C: report_and_quit (m_libcassert.c:136)
> ==9029== by 0x38018C44: panic (m_libcassert.c:210)
> ==9029== by 0x38018CB2: vgPlain_core_panic_at (m_libcassert.c:215)
> ==9029== by 0x38018CD1: vgPlain_core_panic (m_libcassert.c:220)
> ==9029== by 0x380657B4: vgModuleLocal_read_elf_debug_info
> (readelf.c:1193)
> ==9029== by 0x3803644E: vgPlain_di_notify_mmap
> (debuginfo.c:207)
> ==9029== by 0x3804917D:
> vgModuleLocal_generic_PRE_sys_mmap (syswrap-generic.c:1918) ==9029==
> by 0x3805D95A: vgSysWrap_amd64_linux_sys_mmap_before
> (syswrap-amd64-linux.c:944)
> ==9029== by 0x3804D2B2:
> vgPlain_client_syscall (syswrap-main.c:719)
> ==9029== by 0x380387C5:
> vgPlain_scheduler (scheduler.c:721)
> ==9029== by 0x3805A86F:
> run_a_thread_NORETURN (syswrap-linux.c:87)
Ah, that's nothing to do with glibc as such - it's probably the same
problem that somebody reported on the bugtracker the other week where
they had a debuginfo RPM installed and some of the ELF sections that
had been moved to the debuginfo object hadn't been stripped from the
main object properly so they were duplicated.
Look for "repeated section" in bugzilla and you should find it.
Tom
--
Tom Hughes (to...@co...)
http://www.compton.nu/
|