Hi,
I'd like to know what the current state of heap-shot profiling is in
mono (3.12.1). I've been trying to use the heap-shot-gui tool [1] and
it seems pretty broken. Here's what I've tried
## Instructions in heap-shot's README [2]
These tell me to use
$ mono --profile=heap-shot MyProgram.exe
On 31 May 2015 at 17:35, Greg Young gregoryyou...@gmail.com wrote:
What tools are people using with mono? I have tried as an example
using valgrind to verify the stuff I am working on is reasonable but
the listings of problems that come out are massive.
Checking the memory usage via valgrind
On 22 May 2015 at 14:21, Cyd Haselton chasel...@gmail.com wrote:
On May 22, 2015 7:34:16 AM CDT, Jo Shields direct...@apebox.org wrote:
On 22/05/15 01:16, cyd wrote:
Let me back up a few steps before I start troublehooting this.
Does the monolite build of mono 4.0 support
However, when i move TA executable to another machine running ubuntu, and
right click/run, nothing happens. Application won't start, there's no
error message, just nothing...
Can someone help me with this?
Run the application from a terminal to see if it logs any output
indicating some sort
On 3 August 2015 at 12:34, onedevteam.com martin.jere...@gmail.com wrote:
When i try TA or sudo TA in terminal, i get an error TA: command not found,
even if terminal window is open in folder where TA is copied.
The current working directory is not usually is the shell's PATH (the
list of
On 4 August 2015 at 11:23, onedevteam.com martin.jere...@gmail.com wrote:
running with mono myapp.exe is not an option. I wan't application to be
useful on computers with no mono installed.
Meanwhile, i have managed to start application bundled with mkbundle
TestApp --deps --static -o TA on
On 6 November 2015 at 05:29, Rodrigo Kumpera wrote:
> Mono ignores those settings and will run with the bitness it was compiled
> as.
Okay, by "it" I presume you are referring to the target Mono was
compiled for, not the target the application was compiled for.
Hi Ludovic,
On 15 October 2015 at 12:47, Ludovic Henry wrote:
> Hi Dan,
>
> As I am currently working on the Process class, I am getting a look at your
> bug.
Thanks for taking a look :)
>
> Does setting StandardOutputEncoding = Console.OutputEncoding on the
>
Hi,
This is an issue that I was bitten by a while ago but I didn't post
here because I managed to work around it but it looks like something
inside mono changed between 3.12 and 4.0.4 which my broke my
workaround.
The issue basically is I observed my code failing when called from an
NUnit test
Hi,
> I've also got a link to a downloadable .zip file containing the sources and
> the nUnit package for easy compiling on Windows as well as Linux without
> having to create your own project (done due to size restrictions on the
> mailing list). nUnit 2.6.4 is present, so that it compiles
10 matches
Mail list logo