Re: memory corruption
- From: some one <solrak29 yahoo com>
- To: Justin Schoeman <justin expertron co za>
- Cc: orbit-list gnome org
- Subject: Re: memory corruption
- Date: Fri, 28 Nov 2003 10:55:38 -0800 (PST)
Ah, I see that you suspect that buf is being
deallocated twice, thus corrupting memory...?
I took it step further and just assigned buf=NULL
after the g_free call in the function
giop_recv_buffer_unuse(). I will let you know the
results once I can compile orbit again.
But why would the recv_buffer be populated with the
reply status of LOCATION_FORWARD ? Thus taking that
path through the code....
Thanks
--- Justin Schoeman <justin@expertron.co.za> wrote:
> Can you try to delete the line:
>
> giop_recv_buffer_unuse (buf);
>
> around line 361 of orb/orb-core/corba-object.c,
> rebuild ORBit, and see
> what happens. If that doesn't work, could you redo
> the valgrind run
> adding a --num-callers=16 option?
>
> -justin
>
> some one wrote:
> > I can send the source as an attatchment to you or
> > anyone who is interested... if you dont mind
> reviewing
> > the code. The size is only 5K. Sorry I didn't
> > include it in the code snippet, but I do set
> _buffer
> > to NULL.
> >
> > BTW, I would like to step through the code in gdb,
> but
> > gdb complains about not finding the shared
> library. I
> > set the LD_LIBRARY_PATH appropiately and can run
> the
> > program outside of gdb. Any ideas?
> >
> >
> > --- Jan Kratochvil <lace@jankratochvil.net> wrote:
> >
> >>Hi The Mystical Anyone,
> >>
> >>On Thu, 20 Nov 2003 16:07:15 +0100, some one
> wrote:
> >>...
> >>
> >>>My application is just a copy of the echo example
> >>
> >>with
> >>
> >>>a few changes to use a different IOR file and
> call
> >>
> >>to
> >>
> >>>function generated by my IDL in the client_run
> >>>function.
> >>
> >>Why can't you just post the program on some web
> and
> >>provide URL to it?
> >>(to not to post large source file to the list)
> >>
> >>...
> >>
> >>>IDL. Here is a snippet:
> >>>
> >>>CisFigration_v0_BlockSeq* blocks =
> >>>CisFiguration_v0_BlockSeq__alloc();
> >>>
> >>>blocks->_maximum = 0;
> >>>blocks->_length = 0;
> >>
> >>Here is missing
> >> blocks->_buffer = NULL;
> >>
> >>It may corrupt the memory if someone would try to
> >>free 'blocks'.
> >>
> >>
> >>
> >>Lace
> >
> >
> >
> > __________________________________
> > Do you Yahoo!?
> > Free Pop-Up Blocker - Get it now
> > http://companion.yahoo.com/
> > _______________________________________________
> > orbit-list mailing list
> > orbit-list@gnome.org
> > http://mail.gnome.org/mailman/listinfo/orbit-list
> >
>
> _______________________________________________
> orbit-list mailing list
> orbit-list@gnome.org
> http://mail.gnome.org/mailman/listinfo/orbit-list
__________________________________
Do you Yahoo!?
Free Pop-Up Blocker - Get it now
http://companion.yahoo.com/
[
Date Prev][Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]