Re: Another Segfault In GIOP Code

[Michael Meeks <michael ximian com>]

Hi Chris,

On Sat, 2003-05-10 at 05:21, Chris McGee wrote:
> I found another segmentation fault in the GIOP code.

	Ok - this looks like plain and simple memory corruption / a double free
somewhere. I'm hoping this is in your code ;-)

	Here is how to set about finding it:

	a) export MALLOC_CHECK_=2
	re-run your app to see if the stack-trace is more informative

	b) link to electric fence; ensure you add a 'free (malloc(8))'
	to your main function; re-run in gdb likewise.

	c) Download / build 'valgrind' (google for it), and that 
	should nail the problem ( you need to use --alignment=8 ).

	Thanks for chasing this one,

	Regards,

		Michael.

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