> you must do is to call its Initialize() function - this function takes an `IntPtr' > as first argument and we do not know what this is.
This is a pointer to (unmanaged) implementation of IMetaDataEmit interface - it is supposed to be created using COM instantiation methods, that's why it's passed using IntPtr. SMC compiler sources contain some information about this, as well as Unmanaged Metadata API docs (info on emitter). Perhaps Rotor sources could provide some insights as well. ----- Original Message ----- From: "Martin Baulig" <[EMAIL PROTECTED]> To: "Jaroslaw Kowalski" <[EMAIL PROTECTED]> Cc: "Lawrence Pit" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Wednesday, May 22, 2002 3:01 PM Subject: Re: [Mono-list] Source lines in backtraces .... > "Jaroslaw Kowalski" <[EMAIL PROTECTED]> writes: > > > How about using "System.Diagnostics.SymbolStore" to read PDBs on Windows? I > > haven't tried it yet but it looks promising. It should be feasible to create > > a symbol table converter for csc-generated assemblies to dwarf format so > > that you can compile on Windows and debug on Linux for example. > > That's exactly the problem. We're using the "System.Diagnostics.SymbolStore" > interface, but we don't know how to make it work with microsofts symbol writer: > > Once you have an `ISymbolWriter' instance, according to the docu the first thing > you must do is to call its Initialize() function - this function takes an `IntPtr' > as first argument and we do not know what this is. > > Both using `new IntPtr (0)' and not calling the Initialize() function at all failed. > > -- > Martin Baulig > [EMAIL PROTECTED] > > _______________________________________________ > Mono-list maillist - [EMAIL PROTECTED] > http://lists.ximian.com/mailman/listinfo/mono-list > _______________________________________________ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
