|
From: Jianhua Y. <ya...@no...> - 2004-10-21 03:50:06
|
--17784-- INTERNAL ERROR: Valgrind received a signal 11 (SIGSEGV) - = exiting=0A= --17784-- si_code=3D1 Fault EIP: 0xB0052053; Faulting address: = 0x1DC9C000=0A= =0A= valgrind: the `impossible' happened:=0A= Killed by fatal signal=0A= Basic block ctr is approximately 3200000=0A= =3D=3D17784=3D=3D at 0xB002FFDF: vgPlain_core_panic = (vg_mylibc.c:1156)=0A= =3D=3D17784=3D=3D by 0xB002FFDE: panic (vg_mylibc.c:1152)=0A= =3D=3D17784=3D=3D by 0xB002FFFF: vgPlain_core_panic = (vg_mylibc.c:1157)=0A= =3D=3D17784=3D=3D by 0xB00374B0: vg_sync_signalhandler = (vg_signals.c:2191)=0A= =0A= sched status:=0A= =0A= Thread 1: status =3D Runnable, associated_mx =3D 0x0, associated_cv =3D = 0x0=0A= =3D=3D17784=3D=3D at 0x1DC9BC2F: ???=0A= =3D=3D17784=3D=3D by 0x1BDDC8F0: = ACE_MMAP_Memory_Pool::map_file(long) = (/home/zhentao/ACE/ACE_wrappers/ace/Mem_Map.i:9)=0A= =3D=3D17784=3D=3D by 0x1BDDC9BF: = ACE_MMAP_Memory_Pool::acquire(unsigned, unsigned&) = (Memory_Pool.cpp:364)=0A= =3D=3D17784=3D=3D by 0x8071D8F: = SpcBase::SPCMemPool<ACE_MMAP_Memory_Pool, = ACE_Thread_Mutex>::shared_malloc(unsigned) = (../../../spc_base/memory_mgmt/baseSPCMemPool.h:485)=0A= =0A= Thread 2: status =3D WaitSys, associated_mx =3D 0x0, associated_cv =3D = 0x0=0A= =3D=3D17784=3D=3D at 0x1C010CB5: nanosleep (in = /lib/libc-2.3.2.so)=0A= =0A= Thread 3: status =3D WaitSys, associated_mx =3D 0x0, associated_cv =3D = 0x0=0A= =3D=3D17784=3D=3D at 0x1C038BA2: loser_poll (in = /lib/libc-2.3.2.so)=0A= =0A= Thread 4: status =3D WaitSys, associated_mx =3D 0x0, associated_cv =3D = 0x0=0A= =3D=3D17784=3D=3D at 0x1C010CB5: nanosleep (in = /lib/libc-2.3.2.so)=0A= =0A= Thread 5: status =3D WaitCV, associated_mx =3D 0x1C144358, = associated_cv =3D 0x1C144374=0A= =3D=3D17784=3D=3D at 0x1BE454EE: pthread_cond_wait = (vg_libpthread.c:1454)=0A= =0A= Thread 6: status =3D WaitSys, associated_mx =3D 0x0, associated_cv =3D = 0x0=0A= =3D=3D17784=3D=3D at 0x1C03B082: select (in /lib/libc-2.3.2.so)=0A= =0A= =0A= Note: see also the FAQ.txt in the source distribution.=0A= It contains workarounds to several common problems.=0A= =0A= If that doesn't help, please report this bug to: valgrind.kde.org=0A= =0A= In the bug report, send all the above text, the valgrind=0A= version, and what Linux distro you are using. Thanks.=0A= =0A= uname -a result:=0A= Linux wsupd112 2.4.18-3 #1 Thu Apr 18 07:37:53 EDT 2002 i686 unknown=0A= =0A= |
|
From: Tom H. <th...@cy...> - 2004-10-31 10:25:19
|
In message <614...@zs...>
"Jianhua Yang" <ya...@no...> wrote:
> --17784-- INTERNAL ERROR: Valgrind received a signal 11 (SIGSEGV) - exiting
> --17784-- si_code=1 Fault EIP: 0xB0052053; Faulting address: 0x1DC9C000
>
> valgrind: the `impossible' happened:
> Killed by fatal signal
> Basic block ctr is approximately 3200000
> ==17784== at 0xB002FFDF: vgPlain_core_panic (vg_mylibc.c:1156)
> ==17784== by 0xB002FFDE: panic (vg_mylibc.c:1152)
> ==17784== by 0xB002FFFF: vgPlain_core_panic (vg_mylibc.c:1157)
> ==17784== by 0xB00374B0: vg_sync_signalhandler (vg_signals.c:2191)
>
> sched status:
>
> Thread 1: status = Runnable, associated_mx = 0x0, associated_cv = 0x0
> ==17784== at 0x1DC9BC2F: ???
> ==17784== by 0x1BDDC8F0: ACE_MMAP_Memory_Pool::map_file(long) (/home/zhentao/ACE/ACE_wrappers/ace/Mem_Map.i:9)
It's impossible to say for sure but given that this looks like it
is in an mmap operation it is quite possible that this is the skip
list bug I fixed this week.
Can you try this with the CVS head version and see if it is still
happening there - if is then please file a bug on the bug tracker
for this. The CVS version should also give a better stack trace if
it is still happening.
Tom
--
Tom Hughes (th...@cy...)
Software Engineer, Cyberscience Corporation
http://www.cyberscience.com/
|