Hey, That's a good question, it's going to be hard to debug.
Have you thought about adding a scope to the debug information? You'll need at least one lexical scope that covers the entire method body. Jb On Fri, Apr 27, 2018 at 10:23 AM <[email protected]> wrote: > I'm using Cecil to create a managed library from scratch (i.e. I'm not > loading in an existing DLL and modifying it). Using > the PortablePdbWriterProvider from the latest version, and associating file > name & line number information with sequence points in my code, Cecil > outputs a PDB file, but when trying to step into the code from a C# project > in Visual Studio, VS gives the "Source information is missing from the > debug information for this module. > > VS does report "Symbols loaded" when loading my DLL into memory, so it > *appears* to be finding the PDB file. I've also made sure the assembly I've > generated has a DebuggableAttribute set against it. > > If I load the DLL using Cecil, then Cecil reports line numbers against the > instructions as expected which suggests that I've (probably?) added the > sequence points in the correct way. > > Possibly unrelated: If I try to use the PDB2PDB utility to convert the > portable PDB into a non-portable PDB, it fails and reports "Image is too > small". > > Does anybody have suggestions for what I should be trying next to diagnose > the cause of this problem? > > -- > -- > -- > mono-cecil > --- > You received this message because you are subscribed to the Google Groups > "mono-cecil" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- -- -- mono-cecil --- You received this message because you are subscribed to the Google Groups "mono-cecil" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
