[Mono-osx] wrong debug information building on MacOS

pablosantosluac at terra.es pablosantosluac at terra.es
Tue Sep 9 13:52:48 EDT 2008

Hi Rodrigo,

It would be great!

I'm also detecting some problems on PPC related to method calls... 
Depending on the method name (it seems interfaces with "similar 
methods") method invokes tend to fail... Will try to come up with a test 


Rodrigo Kumpera escribió:
> Oh, well, debugging information is one area we lack proper automated 
> testing.
> So it's hard to say if works or not on non x86 machines, or even 
> outside linux/windows,
> as these are the targets most of us use daily.
> Pablo, I don't have access to such machine, but Mark Probst, which 
> have recently
> done some hacking on darwin ppc might be able to help you out.
> Cheers,
> Rodrigo
> On Tue, Sep 9, 2008 at 9:17 AM, pablosantosluac at terra.es 
> <mailto:pablosantosluac at terra.es> <pablosantosluac at terra.es 
> <mailto:pablosantosluac at terra.es>> wrote:
>     Hi,
>     I'm building the plastic server on MacOS X (10.4, PowerPC) in order to
>     debug a problem we've there.
>     Ok, I'm getting an "object not set" and my code prints the stack trace
>     of the exception. For some reason the stack trace prints the right
>     methods but wrong locations: it always points to the same file
>     (and the
>     method is not even there) and the a wrong line number (the line number
>     is much bigger than the line count of the file it mentions).
>     I think it always points to the first file built in the assembly.
>     I'm using mono 2.0
>     Any ideas?
>     Thanks
>     pablo
>     _______________________________________________
>     Mono-osx mailing list
>     Mono-osx at lists.ximian.com <mailto:Mono-osx at lists.ximian.com>
>     http://lists.ximian.com/mailman/listinfo/mono-osx

More information about the Mono-osx mailing list