Win32 Mono 2.0 compiled from SVN branch - dies inside mono_get_lmf_addr

_______________________________________________
Mono-devel-list mailing list
Mono-devel-list <at> lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

[PATCH] eglib memory allocation changes

Hello All,

Attached is a patch to change eglib memory allocation methods to
return NULL if the size is passed in is zero.  If this is approved I
would also like to put it into the 2.0 branch.

I tracked a bug to load_modules in image.c.  In this particular case
image->modules was being set to a non-null value when the
image->module_count was equal to 0.  There is another area of the code
later that checks the modules but not he module_count and causes an
assert.  I could have simply changed this code but after reading the
glib documentation I believe that this patch is the right change.
Also there may be more critical areas that I have not discovered yet
that could hit this problem.

Documentation

malloc
If size is 0, either a null pointer or a unique pointer that can be
successfully passed to free() shall be returned.

calloc
If either nelem or elsize is 0, then either a null pointer or a unique
pointer value that can be successfully passed to free() shall be
returned.

realloc
If size is 0, either a null pointer or a unique pointer that can be
successfully passed to free() shall be returned.
If size is 0 and ptr is not a null pointer, the object pointed to is freed.

g_malloc
If n_bytes is 0 it returns NULL.

g_malloc0 ()
If n_bytes is 0 it returns NULL.

g_realloc ()
n_bytes may be 0, in which case NULL will be returned and mem will be
freed unless it is NULL.

thanks
-bill

_______________________________________________
Mono-devel-list mailing list
Mono-devel-list <at> lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

Re: Win32 Mono 2.0 compiled from SVN branch - dies inside mono_get_lmf_addr

russell.kay <at> realtimeworlds.com wrote:
> All,
> 
>  
> 
> Does anyone have any ideas why I am seeing my code dying inside
> mono_get_lmf_addr at the g_assert_not_reached(), it looks like this code
> has something to do with trampolines but there are not a lot of comments
> around this function.
> 
>  
> 
> I have compiled mono from the 2.0 branch (using cygwin) and everything
> else seems to be working fine, well I am seeing what I expect, just it
> is dying on exit.
> 
>  
> 
> The code that I am running is using System.Timers.Timer, running around
> 10 of them and it dies on exit.

Please file a bug with a test case at http://www.mono-project.com/Bugs.

Robert

mono run time not found

hai,
i am using mono 1.9.1 for windows and vspr2make ver 0.99.0.2 but when i 
click test mono i got error message box that is mono runtime not found 
now what i do pls help me

--

-- 
Thanks & Regards,
Selva kumar.A

Re: [PATCH] eglib memory allocation changes

Hi,

  Approved.

       Zoltan

2008/8/1 Bill Holmes <billholmes54 <at> gmail.com>:
> Hello All,
>
> Attached is a patch to change eglib memory allocation methods to
> return NULL if the size is passed in is zero.  If this is approved I
> would also like to put it into the 2.0 branch.
>
> I tracked a bug to load_modules in image.c.  In this particular case
> image->modules was being set to a non-null value when the
> image->module_count was equal to 0.  There is another area of the code
> later that checks the modules but not he module_count and causes an
> assert.  I could have simply changed this code but after reading the
> glib documentation I believe that this patch is the right change.
> Also there may be more critical areas that I have not discovered yet
> that could hit this problem.
>
> Documentation
>
> malloc
> If size is 0, either a null pointer or a unique pointer that can be
> successfully passed to free() shall be returned.
>
> calloc
> If either nelem or elsize is 0, then either a null pointer or a unique
> pointer value that can be successfully passed to free() shall be
> returned.
>
> realloc
> If size is 0, either a null pointer or a unique pointer that can be
> successfully passed to free() shall be returned.
> If size is 0 and ptr is not a null pointer, the object pointed to is freed.
>
> g_malloc
> If n_bytes is 0 it returns NULL.
>
> g_malloc0 ()
> If n_bytes is 0 it returns NULL.
>
> g_realloc ()
> n_bytes may be 0, in which case NULL will be returned and mem will be
> freed unless it is NULL.
>
> thanks
> -bill
>
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list <at> lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list
>
>

Mono 2.0 Preview 1 is out!!

Hey Everyone,

We've just released Mono 2.0 Preview 1 today! Please help us out by 
giving it a try with your applications.

As always, you can get the preview releases here:
http://mono.ximian.com/monobuild/preview/download-preview/

Please report any bugs that you may find using our Bugs page, AND reply 
to this thread with the bug numbers so we can track them!
http://www.mono-project.com/Bugs

You can see the bugs we're tracking for Mono 2.0 here:
https://bugzilla.novell.com/buglist.cgi?bug_file_loc_type=allwordssubstr&bug_file_loc=http%3A%2F%2Fwww.go-mono.com%2Farchive%2F2.0%2F&order=bugs.bug_status%20

The earlier you file the bugs and reply to this message, the more likely 
your bugs will get fixed.

Special attention is given to regressions, so if you can tell us a 
version of Mono where the bug worked and you tag the summary of the bug 
with [Regression], then it is much more likely your bug will get fixed.

Please help the Mono team to make 2.0 the best ever.

Thanks again!

Mono QA

Re: Mono 2.0 Preview 1 is out!!

To make sure, the release notes contain changes only from 1.9 (unlike
the page title implies), right?

Atsushi Eno

Marc Christensen wrote:
> Hey Everyone,
> 
> We've just released Mono 2.0 Preview 1 today! Please help us out by 
> giving it a try with your applications.
> 
> As always, you can get the preview releases here:
> http://mono.ximian.com/monobuild/preview/download-preview/
> 
> Please report any bugs that you may find using our Bugs page, AND reply 
> to this thread with the bug numbers so we can track them!
> http://www.mono-project.com/Bugs
> 
> You can see the bugs we're tracking for Mono 2.0 here:
> https://bugzilla.novell.com/buglist.cgi?bug_file_loc_type=allwordssubstr&bug_file_loc=http%3A%2F%2Fwww.go-mono.com%2Farchive%2F2.0%2F&order=bugs.bug_status%20
> 
> The earlier you file the bugs and reply to this message, the more likely 
> your bugs will get fixed.
> 
> Special attention is given to regressions, so if you can tell us a 
> version of Mono where the bug worked and you tag the summary of the bug 
> with [Regression], then it is much more likely your bug will get fixed.
> 
> Please help the Mono team to make 2.0 the best ever.
> 
> Thanks again!
> 
> Mono QA
> 
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list <at> lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list
> 

Re: Mono 2.0 Preview 1 is out!!

Hello,

> To make sure, the release notes contain changes only from 1.9 (unlike
> the page title implies), right?

The release notes includes changes since 1.9, and contains links to the
full changes since 1.2.0

Should I get all the release for previous releases consolidated?

> Atsushi Eno
> 
> Marc Christensen wrote:
> > Hey Everyone,
> > 
> > We've just released Mono 2.0 Preview 1 today! Please help us out by 
> > giving it a try with your applications.
> > 
> > As always, you can get the preview releases here:
> > http://mono.ximian.com/monobuild/preview/download-preview/
> > 
> > Please report any bugs that you may find using our Bugs page, AND reply 
> > to this thread with the bug numbers so we can track them!
> > http://www.mono-project.com/Bugs
> > 
> > You can see the bugs we're tracking for Mono 2.0 here:
> > https://bugzilla.novell.com/buglist.cgi?bug_file_loc_type=allwordssubstr&bug_file_loc=http%3A%2F%2Fwww.go-mono.com%2Farchive%2F2.0%2F&order=bugs.bug_status%20
> > 
> > The earlier you file the bugs and reply to this message, the more likely 
> > your bugs will get fixed.
> > 
> > Special attention is given to regressions, so if you can tell us a 
> > version of Mono where the bug worked and you tag the summary of the bug 
> > with [Regression], then it is much more likely your bug will get fixed.
> > 
> > Please help the Mono team to make 2.0 the best ever.
> > 
> > Thanks again!
> > 
> > Mono QA
> > 
> > _______________________________________________
> > Mono-devel-list mailing list
> > Mono-devel-list <at> lists.ximian.com
> > http://lists.ximian.com/mailman/listinfo/mono-devel-list
> > 
> 
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list <at> lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list

Re: [PATCH] eglib memory allocation changes

Hello,

> I tracked a bug to load_modules in image.c.  In this particular case
> image->modules was being set to a non-null value when the
> image->module_count was equal to 0.  There is another area of the code
> later that checks the modules but not he module_count and causes an
> assert.  I could have simply changed this code but after reading the
> glib documentation I believe that this patch is the right change.
> Also there may be more critical areas that I have not discovered yet
> that could hit this problem.

It would be useful to add unit test cases so this behavior is also
enforced in the code.  Mind adding those?

Miguel.

Re: Mono 2.0 Preview 1 is out!!

Hey,

When 1.2 was released, we had somewhat summarized version of
the release notes which describes difference from 1.0.
I was wondering this time if we are to write similar one as well,
and put such one as the final release notes. Current document content
is (should be) different, while the title implies as if it were for
the final release notes.

IMO current release notes (including the document title) should be
distinguished from the final one.

Atsushi Eno

Miguel de Icaza wrote:
> Hello,
> 
>> To make sure, the release notes contain changes only from 1.9 (unlike
>> the page title implies), right?
> 
> The release notes includes changes since 1.9, and contains links to the
> full changes since 1.2.0
> 
> Should I get all the release for previous releases consolidated?
> 
>> Atsushi Eno
>>
>> Marc Christensen wrote:
>>> Hey Everyone,
>>>
>>> We've just released Mono 2.0 Preview 1 today! Please help us out by 
>>> giving it a try with your applications.
>>>
>>> As always, you can get the preview releases here:
>>> http://mono.ximian.com/monobuild/preview/download-preview/
>>>
>>> Please report any bugs that you may find using our Bugs page, AND reply 
>>> to this thread with the bug numbers so we can track them!
>>> http://www.mono-project.com/Bugs
>>>
>>> You can see the bugs we're tracking for Mono 2.0 here:
>>> https://bugzilla.novell.com/buglist.cgi?bug_file_loc_type=allwordssubstr&bug_file_loc=http%3A%2F%2Fwww.go-mono.com%2Farchive%2F2.0%2F&order=bugs.bug_status%20
>>>
>>> The earlier you file the bugs and reply to this message, the more likely 
>>> your bugs will get fixed.
>>>
>>> Special attention is given to regressions, so if you can tell us a 
>>> version of Mono where the bug worked and you tag the summary of the bug 
>>> with [Regression], then it is much more likely your bug will get fixed.
>>>
>>> Please help the Mono team to make 2.0 the best ever.
>>>
>>> Thanks again!
>>>
>>> Mono QA
>>>
>>> _______________________________________________
>>> Mono-devel-list mailing list
>>> Mono-devel-list <at> lists.ximian.com
>>> http://lists.ximian.com/mailman/listinfo/mono-devel-list
>>>
>> _______________________________________________
>> Mono-devel-list mailing list
>> Mono-devel-list <at> lists.ximian.com
>> http://lists.ximian.com/mailman/listinfo/mono-devel-list
> 
>