[Mono-list] Question concerning portability
neil.young at freenet.de
Tue Jun 24 12:20:32 EDT 2008
Andy Hume wrote:
> neil.young wrote:
>> OK, the disappointment is great.
>> 1) MOMA check => OK
>> 2) Application runs perfectly under Windows Mono 1.9
>> 3) Booted with OpenSUSE 10.3/Mono 1.91, got the windows assemblies from
>> memory stick and launched it...
>> 4) Result: Object reference not set bla bla
>> 5) --trace=ALL: Null pointer exception
>> 6) --verbose: Out of memory (?)
>> Isn't there someting usefull, like a stacktrace or so?
> ---debug should do the trick. :-)
> Or what are you seeing exactly at step 4? Just the message? Is there
> some catch in the app that's handling the exception and thus the CLR
> doesn't get an unhandled exceptoin to print?
> Have you see the good guide at
> http://www.mono-project.com/Guide:_Porting_Winforms_Applications , it
> recommends mono XXX.exe 2> log.txt, maybe that has the most important
> effect as --debug; i.e. stopping the app from detaching from the console,
> and thus no errors can be seen.
> On the accessing the Windows PC disks issue -- althought you may be
> discussing that in another thread I think? -- I have my Windows drives
> shared on the network and use Samba to mount them from the virtual
> machine. To start with one can use smbclient which acts like a ftp
> client, then if that works one can mount the drives permanently. That
> needs the VM networking working of course, the virtual driver works here
> and Linux picks up a address by DHCP from my local router (on resuming the
> the address often needs refreshed by running dhclient manually).
> Both the guide referenced above and
> http://www.mono-project.com/VMware_Image recommend connecting *to* the
> Linux VM with Samba. Which may indeed be easier...
thanks for the answer.
>Or what are you seeing exactly at step 4? Just the message? Is there some
catch in the app that's >handling the exception and thus the CLR doesn't get
an unhandled exceptoin to print?
Exactly just that "Object reference not set..." - the nul pointer exception.
My code is full of try catch and yes - thanks for the clue - probably I
should throw it finally to the clr after tracing the error. Or at least not
trace just ex.Message, but ex.ToString() instead. Thanks for pointing out
the obvious :)
Let you know.
View this message in context: http://www.nabble.com/Question-concerning-portability-tp18043465p18094548.html
Sent from the Mono - General mailing list archive at Nabble.com.
More information about the Mono-list