Re: crash on resize



On Tue, Jul 19, 2005 at 02:21:40PM +0300, Pavel Tsekov wrote:
> > > any idea?
> >
> > Yes. Bad slang.
> >
> > https://savannah.gnu.org/bugs/?func=detailitem&item_id=13788
> 
> Did it help or is it something else that you are seeing ?
>
mcslang works fine; the valgrind messages are also gone. thx.

fwiw, there is still another message from valgrind right at the start:

==26269== Invalid read of size 4
==26269==    at 0x190FF968: (within /lib/ld-2.3.2.so)
==26269==    by 0x41121059: (within /lib/tls/libc-2.3.2.so)
==26269==    by 0x190FA015: _dl_catch_error (in /lib/ld-2.3.2.so)
==26269==    by 0x41120ED5: _dl_open (in /lib/tls/libc-2.3.2.so)
==26269==    by 0x41186037: (within /lib/tls/libdl-2.3.2.so)
==26269==    by 0x190FA015: _dl_catch_error (in /lib/ld-2.3.2.so)
==26269==    by 0x411864A5: (within /lib/tls/libdl-2.3.2.so)
==26269==    by 0x41185FE3: dlopen (in /lib/tls/libdl-2.3.2.so)
==26269==  Address 0x1923C0A0 is 8 bytes inside a block of size 10 alloc'd
==26269==    at 0x191099F6: malloc (vg_replace_malloc.c:149)
==26269==    by 0x19152926: g_malloc (in /usr/lib/libglib-2.0.so.0.600.5)
==26269==    by 0x19162918: g_strdup (in /usr/lib/libglib-2.0.so.0.600.5)
==26269==    by 0x19125C27: g_module_open (in /usr/lib/libgmodule-2.0.so.0.600.5)
==26269==    by 0x80876D5: x11_available (x11conn.c:135)
==26269==    by 0x8087813: mc_XOpenDisplay (x11conn.c:181)
==26269==    by 0x806CC5D: init_key (key.c:415)
==26269==    by 0x80708F9: main (main.c:2165)

looks like a glibc or glib bug, though. it doesn't seem to cause
problems, either.

-- 
Hi! I'm a .signature virus! Copy me into your ~/.signature, please!
--
Chaos, panic, and disorder - my work here is done.



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]