Debugging

Debugging

Postby _Retaliate_ » 28 Jul 2014, 13:11

I've seen that most of the errors that occur in MCDzienny do not have the line or file in which the error occured.
So, from that, I would suggest generating a pdb for MCDzienny_.dll, in order to be able to show the line and column as well as the file in which the error occured in. You could additionally make it easier for custom command makers to debug their code by adding a pdb for the dlls generated by /compile as well.
Honestly, I have no idea how you would go about doing this. Making a pdb for MCDzienny_.dll would be easy using visual studio. I would guess that CSharpCodeProvider has an option for generating a pdb.

This would just make it easier for developers such as myself to debug their code and as well as making it easier for you to debug your code when people report problems.
Image
_Retaliate_
 
Posts: 68
Joined: 26 Sep 2013, 11:16

Re: Debugging

Postby dzienny » 28 Jul 2014, 22:31

It's actually a very good idea <ok>. The next release will implement it, so that the compile command will also generate a pdb file.
User avatar
dzienny
Administrator
 
Posts: 1181
Joined: 23 Jan 2011, 14:27


Return to General Suggestions

Who is online

Users browsing this forum: No registered users and 1 guest

cron