Hello Miguel, I also had to apply this change in order to avoid an unallowed warning > message: > > I: Statement might be overflowing a buffer in strncat. Common mistake: > > BAD: strncat(buffer,charptr,sizeof(buffer)) is wrong, it takes the > > left over size as 3rd argument > > GOOD: strncat(buffer,charptr,sizeof(buffer)-strlen(buffer)-1) >
We replaced that code with the glib string operations just yesterday: 042ddd504c09977682bb48010c5642390826d1da But thanks for sharing. > At this point I’m able to build mono RPM packages and they’re working as I > install them using a test OpenSUSE 12.3 virtual machine. However, when the > GTK# builds are started –which use the mono packages as build requirement–, > the worker is unable to run the mono executable: apparently, malloc is > corrupting the heap or something. This is a sample execution as extracted > from the OBS build logs: > > [ 101s] + /opt/plasticscm5/mono/bin/mono > /opt/plasticscm5/mono/lib/mono/4.5/gacutil.exe -l > > [ 101s] *** Error in `/opt/plasticscm5/mono/bin/mono': malloc: top chunk is > corrupt: 0x08ab9230 *** > > What you want to do at this point in time is to run the process under gdb, as this will show where malloc detected the error, and then you should get both the unmanaged stack trace, and if possible the managed one (with the mono_stack gdb macro) Miguel.
_______________________________________________ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
