Random memory allocation error

2009-12-26 Thread Shawn Bakhtiar




At what appears to be random locations in a program which runs thought 24000 
components, and breaking out the formulas in to there raw material components 
(formulations table of about 200,000 formulation lines, I see this error 
message:

malloc: *** error for object 0xe41074: incorrect checksum for freed object - 
object was probably modified after being freed.*** set a breakpoint in 
malloc_error_break to debug
so far I have only found some obscure references, and this is happening 
randomly:
IE
#0  0x95f95072 in malloc_error_break ()#1  0x95f96218 in szone_error ()#2  
0x95f9638b in free_list_checksum_botch ()#3  0x95ea2985 in 
tiny_malloc_from_free_list ()#4  0x95ea1b03 in szone_malloc_should_clear ()#5  
0x95ea1988 in malloc_zone_malloc ()#6  0x95e9fa58 in malloc ()#7  0x00c2a799 in 
g_malloc ()#8  0x00ba774d in g_object_newv ()#9  0x00ba7ef7 in 
g_object_new_valist ()#10 0x00ba758f in g_object_new ()#11 0x000a8468 in 
isi_database_get_component_simple (self=0x101c000, aid=0x2008030 "ZH", 
nid=90005) at isidatabase.c:4296

but it has run through the same piece of code with no problems for 30 times 
before it hits this. continue, and it will go past this part and break ,
#0  0x95f95072 in malloc_error_break ()#1  0x95f96218 in szone_error ()#2  
0x95f9638b in free_list_checksum_botch ()#3  0x95ea2985 in 
tiny_malloc_from_free_list ()#4  0x95ea1b03 in szone_malloc_should_clear ()#5  
0x95ea386b in malloc_zone_calloc ()#6  0x95ea37fa in calloc ()#7  0x00c2a82a in 
g_malloc0 ()#8  0x00053030 in isi_list_instance_init (instance=0x185f190, 
g_class=0xe1a850) at isilist.c:96#9  0x00bc196c in g_type_create_instance ()#10 
0x00ba832a in g_object_constructor ()#11 0x00ba7726 in g_object_newv ()#12 
0x00ba7ef7 in g_object_new_valist ()#13 0x00ba758f in g_object_new ()#14 
0x0005b647 in isi_component_instance_init (instance=0x180e020, 
g_class=0x13a12070) at isicomponent.c:156#15 0x00bc196c in 
g_type_create_instance ()#16 0x00ba832a in g_object_constructor ()#17 
0x00ba7a5e in g_object_newv ()#18 0x00ba7ef7 in g_object_new_valist ()#19 
0x00ba758f in g_object_new ()#20 0x000a8468 in 
isi_database_get_component_simple (self=0x101c000, aid=0x20081b0 "ZH", 
nid=90004) 
 at isidatabase.c:4296#21 0xcd36 in isi_util_normalize_formuals 
(theApp=0x1016010, prompt=1) at isiutil.c:368#22 0xd67f in main (argc=1, 
argv=0xbfffe848) at isiutil.c:764




 EMAILING FOR THE GREATER GOOD
Join me   
___
gtk-app-devel-list mailing list
gtk-app-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list


Re: Random memory allocation error

2009-12-26 Thread Allin Cottrell

On Sat, 26 Dec 2009, Shawn Bakhtiar wrote:

> At what appears to be random locations in a program which runs
> thought 24000 components, and breaking out the formulas in to
> there raw material components (formulations table of about
> 200,000 formulation lines, I see this error message:
>
> malloc: *** error for object 0xe41074: incorrect checksum for
> freed object - object was probably modified after being
> freed.***

Your code is buggy.  Run it under valgrind and you'll see where
the bugs are.

Allin Cottrell
___
gtk-app-devel-list mailing list
gtk-app-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list


RE: Random memory allocation error

2009-12-26 Thread Shawn Bakhtiar



Nailed it on the head. bad programing.
I forgot how wonderful valgrind is, thanks.


 EMAILING FOR THE GREATER GOOD
Join me

> Date: Sat, 26 Dec 2009 13:52:06 -0500
> From: cottr...@wfu.edu
> To: shashan...@hotmail.com
> CC: gtk-app-devel-list@gnome.org; gtk-osx-us...@lists.sourceforge.net
> Subject: Re: Random memory allocation error
> 
> 
> On Sat, 26 Dec 2009, Shawn Bakhtiar wrote:
> 
> > At what appears to be random locations in a program which runs
> > thought 24000 components, and breaking out the formulas in to
> > there raw material components (formulations table of about
> > 200,000 formulation lines, I see this error message:
> >
> > malloc: *** error for object 0xe41074: incorrect checksum for
> > freed object - object was probably modified after being
> > freed.***
> 
> Your code is buggy.  Run it under valgrind and you'll see where
> the bugs are.
> 
> Allin Cottrell
  
___
gtk-app-devel-list mailing list
gtk-app-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list