Re: random commits to ORBit stable




On Thu, 2002-02-07 at 13:16, Sebastian Wilhelmi wrote:
> Ok, only morons reply to themselves, so here we go:

	It's nice to be in good company then.

	It seems likely to me that the change causes a buffer overrun somewhere
to surface in some other code, either way Dobey was getting some pretty
evil traces that went away with electric fence [ the worst kind of
memory pool corruption ], and _MALLOC_CHECK=2 didn't help either.

	Thing is he's not really doing any marshaling at all, so I don't see
how this will help much - but his trace was:

#0  chunk_alloc (ar_ptr=0xfe21da0, nb=24) at malloc.c:2905
#1  0xfd6da40 in __libc_calloc (n=3, elem_size=24) at malloc.c:3840
#2  0xff3e3c0 in g_malloc0 (size=20) at gmem.c:242
#3  0xffaa2f4 in dynany_create (type=0x10014e80, value=0x10017878, 
    parent=0x10015238, ev=0x7ffff598) at dynany.c:595
#4  0xffac904 in DynamicAny_DynAny_current_component (obj=0x3,
ev=0x7ffff598)
    at dynany.c:1198
#5  0x10003b48 in test_struct (orb=0x3, ev=0x7ffff598) at
test-dynany.c:550
#6  0x100040d4 in main (argc=1, argv=0x10015528) at test-dynany.c:607
#7  0xfd11060 in __libc_start_main (argc=1, ubp_av=0x7ffff624, 
    ubp_ev=0x1000018, auxvec=0x7ffff714, rtld_fini=0x3
<__strtol_internal+3>, 
    stinfo=0x100041f8, stack_on_entry=0xffc7a10)
    at ../sysdeps/powerpc/elf/libc-start.c:119

	Gloriously not useful, ( that's from the test-dynany regression test on
PPC ).

	Thanks for the fix,

		Michael.

-- 
 mmeeks@gnu.org  <><, Pseudo Engineer, itinerant idiot




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