[MonoDevelop] How to debug MonoDevelop "native" on Mac?

[Sandy Armstrong]

On 01/08/2009 11:39 AM, Harold Johnson wrote:
> On Thu, Jan 8, 2009 at 11:24 AM, Sandy Armstrong
> <sanfordarmstrong at gmail.com>  wrote:
>> On 01/08/2009 11:03 AM, Herald wrote:
>>> The "native" Mac MonoDevelop app crashes left and right on my system;
>>> someone
>>> suggested I collect the stack traces when it crashes, and file bug
>>> reports.
>>> I'm researching how to do this now, reading
>>> http://www.mono-project.com/Debugging about debugging Mono , where it
>>> instructs us that " it is necessary to compile your programs with
>>> debugging
>>> information." Has the "native" Mac MonoDevelop package been compiled with
>>> debugging information so that I may apply the stack traces to it? If so,
>>> what command do I run in Terminal.app (which is Mac's console
>>> application)?
>>> Thanks.
>> I don't know if the .mdb (debugging) files are included in the
>> MonoDevelop.app; if they were you would want to add --debug in the mono
>> command line of /Applications/MonoDevelop.app/Contents/MacOS/monodevelop .
>>
>> You can still get a useful stack trace even without debug information (it
>> just won't have line numbers and other niceties).
>>
>> Either way, the output will go to Console.app.  Or, if you prefer, you can
>> run the monodevelop script I mention above directly from Terminal.app.
>
> When I run the command I receive the following error:
>
> Cannot open assembly 'monodevelop': File does not contain a valid CIL image.

/Applications/MonoDevelop.app/Contents/MacOS/monodevelop is a shell 
script that start MonoDevelop.  Just execute it directly (it sounds like 
you're trying to run it with mono).  Edit the script to use --debug (I 
think in the last line? I don't have it in front of me), if you want 
better traces.

> How can I confirm that the .mdb files exist/don't exist?

Poke around inside the MonoDevelop.app contents.  They would be with the 
MonoDevelop DLLs and EXEs.

Sandy