Bug 59468 - We should ship mdbdump.exe in our SDK
Summary: We should ship mdbdump.exe in our SDK
Status: RESOLVED NOT_ON_ROADMAP
Alias: None
Product: Tools
Classification: Mono
Component: other ()
Version: unspecified
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Marek Safar
URL:
Depends on:
Blocks:
 
Reported: 2017-09-13 19:20 UTC by Chris King
Modified: 2017-09-22 18:18 UTC (History)
2 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on GitHub or Developer Community with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED NOT_ON_ROADMAP

Description Chris King 2017-09-13 19:20:50 UTC
I expect mono tooling with analogous functionality to the desktop tooling to ship the mono tooling should the desktop tooling also be shipped. Actually, the desktop ships ILDasm while mono does not ship mdbdump; Ildasm offers the /source switch which will interleave source and IL. Monodump offers the same functionality but is not shipped. 

Although the build of mdbdump is fairly simple, it's not drop dead trivial. See slack thread: https://xamarinhq.slack.com/archives/C03CELHQQ/p1505328003000260

This functionality is useful for debugging debugger issues. See slack channel: https://xamarinhq.slack.com/archives/C6WEH8DHN/p1505328168000098
Comment 1 Chris King 2017-09-13 19:35:32 UTC
Oops. I meant to say, if the desktop .NET CLR ships a tool (like ILDasm), and we have a tool with similar functionality (like mdbdump), then we should ship it. 

If the .NET CLR considers the functionality of the tool useful enough to ship, then so should we.
Comment 2 Marek Safar 2017-09-22 18:18:56 UTC
We are promoting pdb instead of mdb now so the need for this tool is even smaller. With this in mind, I don't think it's a good idea to start shipping a new tool which we already know has very limited usage and lock ourselves to keep supporting it for very long time