Hi,
I've split the patches up based on their content. Attached.
unused-functions.patch - #if 0 unused functions in dlmalloc.c and
strtod.c
uninitialized-fixes.patch - make sure variables are initialized with
NULL/0 where used without initialization
mono-printf-fixes.patch - make sure a fo
So it turns out that this is really defined in etc/mono/config and the
OS X packaging scripts will munge that to create the Framework install.
So I suggest we update the config.in with a os="osx" addition and
update the line in the release scripts to reflect the proper dylib.
Patches attach
That makes sense, I'll split them up.
-- Christian
On Aug 4, 2009, at 6:11 AM, Rodrigo Kumpera wrote:
> Hi Chistian,
>
> Your patch is full of very different kind of changes, some are
> simple, others require some thought
> about. So let's sort them into smaller and centered patches.
>
> For e
People are already working on porting to non-linux targets.
On Tue, Aug 4, 2009 at 3:27 PM, Евгений Гришуль wrote:
> Mono profiler still not work (runtime crash at app exit) on some
> mainstream platforms like Mac OS 10.5. May it will be better to enhance
> profiling support on most OSes before b
Mono profiler still not work (runtime crash at app exit) on some
mainstream platforms like Mac OS 10.5. May it will be better to enhance
profiling support on most OSes before building GUI tool?
2009/8/4 Mike Kestner
> We're seeking the input of profiler users and other interested parties
> to hel
We're seeking the input of profiler users and other interested parties
to help create a visual profiling tool for mono applications.
Development is under way in the mono-tools module alongside the current
command line decoder. The tool is a UI to interact with the built-in
mono logging profiler an
On Tue, Aug 4, 2009 at 3:40 PM, Maciej Paszta wrote:
>
> Maybe you don't have GDB installed, which is used to get a richer crash
>> dump.
>>
>
> GDB is installed but when debug info from GDB is about to be generated -
> everything freezes and stays that way.
>
Just for the record - GDB generates
> Maybe you don't have GDB installed, which is used to get a richer crash
> dump.
>
GDB is installed but when debug info from GDB is about to be generated -
everything freezes and stays that way.
--
Maciej Paszta
___
Mono-devel-list mailing list
Mono-d
Hi Chistian,
Your patch is full of very different kind of changes, some are simple,
others require some thought
about. So let's sort them into smaller and centered patches.
For example, the ones changing printf style calls are mostly ok and should
be committed on their
own. Then we can see the wa
On Tue, Aug 4, 2009 at 9:49 AM, Maciej Paszta wrote:
>
>
> On Tue, Aug 4, 2009 at 2:07 PM, Zoltan Varga wrote:
>
>> Hi,
>>
>> You can try compiling mono from source, so the runtime has debugging
>> symbols, so you
>> get more meaningfull stacktraces.
>
>
> I'm actually compiling from the sourc
On Tue, Aug 4, 2009 at 2:07 PM, Zoltan Varga wrote:
> Hi,
>
> You can try compiling mono from source, so the runtime has debugging
> symbols, so you
> get more meaningfull stacktraces.
I'm actually compiling from the source, but no more info is produced. Is
there any option I should pass to .
Hi,
You can try compiling mono from source, so the runtime has debugging
symbols, so you
get more meaningfull stacktraces.
Zoltan
On Tue, Aug 4, 2009 at 12:31 PM, Maciej Paszta wrote:
> Hi!
>
> I've written a custom server software that handles several connections a
Fixed in r139338
--Jérémie Laval
jeremie.la...@gmail.com
http://garuma.wordpress.com
On Tue, Aug 4, 2009 at 3:33 AM, Tony Alexander Hild
wrote:
Hi,
I can't build from trunk due this exception
make[8]: Entering directory `/home/tony/mono/mcs/class/corlib'
Hi!
I've written a custom server software that handles several connections and
processes data that is sent across them. Application is running on mono
2.4.2.2 on debian unstable (amd64). From time to time mono tends to throw
native stack trace:
mono [0x47ea60]
mono [0x4aec9d]
Oh thats handy. Anyone have objections to committing this?
-- Christian
On Aug 4, 2009, at 1:19 AM, Robert Jordan wrote:
> Hi Christian,
>
> Christian Hergert wrote:
>> It looks like Mono.Cairo is trying to load libcairo.so.2 on OS X.
>> Creating the following Mono.Cairo.dll.config works for me
Hi Christian,
Christian Hergert wrote:
> It looks like Mono.Cairo is trying to load libcairo.so.2 on OS X.
> Creating the following Mono.Cairo.dll.config works for me.
>
>
>
>
>
> However, I'm not sure how to go around making a proper patch as you
> folks would like it. The reason I
Is anything else needed to get this patch in?
Thanks,
Adam
On Thu, Jul 23, 2009 at 12:57 PM, Adam Wendt wrote:
> Attached is full patch including ChangeLog and Tests
>
>
> On Thu, Jul 23, 2009 at 12:25 PM, Adam Wendt wrote:
>
>> Here is test case patch: http://pastebin.com/m15952d84
>>
>>
>> On
It looks like Mono.Cairo is trying to load libcairo.so.2 on OS X.
Creating the following Mono.Cairo.dll.config works for me.
However, I'm not sure how to go around making a proper patch as you
folks would like it. The reason I ask is because I don't see any
other dll's in mcs/class/
18 matches
Mail list logo