|
From: Brian C. <cr...@fi...> - 2005-09-07 16:17:16
|
My program, after a few hours of running, causes SVN valgrind to crash in the following way: valgrind: vg_memory.c:229 (vgPlain_unmap_range): Assertion `rs == s' failed. ==8613== at 0xB002BFE0: vgPlain_skin_assert_fail (vg_mylibc.c:1137) ==8613== by 0xB002BFDF: assert_fail (vg_mylibc.c:1133) ==8613== by 0xB002C01D: vgPlain_core_assert_fail (vg_mylibc.c:1144) ==8613== by 0xB0029669: vgPlain_unmap_range (vg_memory.c:229) sched status: Thread 1: status = Runnable, associated_mx = 0x0, associated_cv = 0x0 ==8613== at 0x420E49D1: munmap (in /lib/i686/libc-2.2.5.so) ==8613== by 0x4207531C: _IO_file_close_it@@GLIBC_2.1 (in /lib/i686/libc-2.2.5.so) ==8613== by 0x4206B5D0: _IO_fclose@@GLIBC_2.1 (in /lib/i686/libc-2.2.5.so) ==8613== by 0x809B94C: start_npc_prog (dmpl.c:4058) Thread 2: status = WaitSys, associated_mx = 0x0, associated_cv = 0x0 ==8613== at 0x420B4CA1: nanosleep (in /lib/i686/libc-2.2.5.so) ==8613== by 0x825E6C5: queued_thread_main (threads.c:28) ==8613== by 0x1B93AB39: thread_wrapper (vg_libpthread.c:867) ==8613== by 0xB000F0C3: (within /usr/local/lib/valgrind/stage2) From my googling, this looks like an old bug (91028) which has regressed, but I haven't dug into the code yet. Any thoughts? Thanks in advance, Brian |
|
From: Christoph B. <bar...@or...> - 2005-12-05 22:16:49
|
Hi, I've just got the following error with valgrind 3.1.0: ==01:02:38:32.373 2400== Warning: set address range perms: large range 268439552, a 1, v 1 ==01:02:50:00.615 2400== Warning: set address range perms: large range 268439552, a 0, v 0 --01:02:52:57.936 2400-- INTERNAL ERROR: Valgrind received a signal 7 (SIGBUS) - exiting --01:02:52:57.936 2400-- si_code=2; Faulting address: 0x4F4029EC; sp: 0x495A44610 valgrind: the 'impossible' happened: Killed by fatal signal ==01:02:52:57.936 2400== at 0x700C0FCD: disInstr_AMD64 (toIR.c:7954) ==01:02:52:57.936 2400== by 0x7008F238: bb_to_IR (bb_to_IR.c:187) ==01:02:52:57.936 2400== by 0x700688E5: LibVEX_Translate (vex_main.c:416) ==01:02:52:57.936 2400== by 0x7002354D: vgPlain_translate (libvex_basictypes.h:154) ==01:02:52:57.936 2400== by 0x70034759: handle_tt_miss (scheduler.c:596) ==01:02:52:57.936 2400== by 0x70034B81: vgPlain_scheduler (scheduler.c:717) ==01:02:52:57.936 2400== by 0x7004785E: thread_wrapper (syswrap-linux.c:86) ==01:02:52:57.936 2400== by 0x70047955: run_a_thread_NORETURN (syswrap-linux.c:119) ==01:02:52:57.936 2400== by 0x70047A86: vgModuleLocal_start_thread_NORETURN (syswrap-linux.c:206) ==01:02:52:57.936 2400== by 0x70050F2E: (within /usr/local/opt/x86_64-20050615/lib/valgrind/amd64-linux/memcheck) sched status: running_tid=3 What could be wrong, and how to avoid it? Christoph Bartochek |
|
From: Tom H. <to...@co...> - 2005-12-11 14:55:12
|
In message <200...@or...>
Christoph Bartoschek <bar...@or...> wrote:
> I've just got the following error with valgrind 3.1.0:
Could you raise a bug for it please...
> ==01:02:38:32.373 2400== Warning: set address range perms: large range
> 268439552, a 1, v 1
> ==01:02:50:00.615 2400== Warning: set address range perms: large range
> 268439552, a 0, v 0
> --01:02:52:57.936 2400-- INTERNAL ERROR: Valgrind received a signal 7 (SIGBUS)
> - exiting
Any time you get an INTERNAL ERROR message like that you have found
a bug of some sort in valgrind and you should open a bug for it.
Thanks,
Tom
--
Tom Hughes (to...@co...)
http://www.compton.nu/
|
|
From: Brian C. <cr...@fi...> - 2005-09-07 16:26:29
|
Actually, my apologies.... I was running an old version of valgrind accidentally. *blush* -- Brian Brian Crowder wrote: > > My program, after a few hours of running, causes SVN valgrind to crash > in the following way: > > valgrind: vg_memory.c:229 (vgPlain_unmap_range): Assertion `rs == s' > failed. > ==8613== at 0xB002BFE0: vgPlain_skin_assert_fail (vg_mylibc.c:1137) > ==8613== by 0xB002BFDF: assert_fail (vg_mylibc.c:1133) > ==8613== by 0xB002C01D: vgPlain_core_assert_fail (vg_mylibc.c:1144) > ==8613== by 0xB0029669: vgPlain_unmap_range (vg_memory.c:229) > > sched status: > > Thread 1: status = Runnable, associated_mx = 0x0, associated_cv = 0x0 > ==8613== at 0x420E49D1: munmap (in /lib/i686/libc-2.2.5.so) > ==8613== by 0x4207531C: _IO_file_close_it@@GLIBC_2.1 (in > /lib/i686/libc-2.2.5.so) > ==8613== by 0x4206B5D0: _IO_fclose@@GLIBC_2.1 (in > /lib/i686/libc-2.2.5.so) > ==8613== by 0x809B94C: start_npc_prog (dmpl.c:4058) > > Thread 2: status = WaitSys, associated_mx = 0x0, associated_cv = 0x0 > ==8613== at 0x420B4CA1: nanosleep (in /lib/i686/libc-2.2.5.so) > ==8613== by 0x825E6C5: queued_thread_main (threads.c:28) > ==8613== by 0x1B93AB39: thread_wrapper (vg_libpthread.c:867) > ==8613== by 0xB000F0C3: (within /usr/local/lib/valgrind/stage2) > > > From my googling, this looks like an old bug (91028) which has > regressed, but I haven't dug into the code yet. Any thoughts? > > Thanks in advance, > Brian > > > ------------------------------------------------------- > SF.Net email is Sponsored by the Better Software Conference & EXPO > September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices > Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA > Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf > _______________________________________________ > Valgrind-users mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-users > > > |