Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Review/update documentation of the 'debug' C# compiler option #6773

Closed
cremor opened this issue Aug 1, 2018 · 18 comments · Fixed by #22797 or #23509
Closed

Review/update documentation of the 'debug' C# compiler option #6773

cremor opened this issue Aug 1, 2018 · 18 comments · Fixed by #22797 or #23509
Assignees
Labels
doc-bug Problem with the content; needs to be fixed [org][type][category] dotnet-csharp/svc errors-warnings/subsvc Pri2

Comments

@cremor
Copy link

cremor commented Aug 1, 2018

Could you please review this page and make sure that it is actually correct? Because there are a few posts that claim that parts of that documentation is wrong or outdated.

A good starting point is this question on StackOverflow. The two highest voted answers both say that this documentation is outdated and they also provide links to further information.


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

@rpetrusha
Copy link
Contributor

Thanks, @cremor, for your feedback. We'll have to investigate before we can revise the documentation.

@tmat
Copy link
Member

tmat commented Aug 9, 2018

https://github.com/dotnet/roslyn/blob/master/docs/compilers/CSharp/CommandLine.md has up to date documentation of the switch.

@BillWagner
Copy link
Member

The current doc is missing /debug:portable and /debug:embedded descriptions.

The other key change i that /debug:pdbonly should be called out as a Windows only debug format. The /debug:portable would be preferred.

@tmat
Copy link
Member

tmat commented Aug 10, 2018

Also /debug:pdbonly is exactly the same as /debug:full. It's not really a Windows-only switch.
It will produce Portable PDB on Linux and Windows PDB on Windows.

@tmat
Copy link
Member

tmat commented Aug 10, 2018

You can link https://github.com/dotnet/designs/blob/master/accepted/diagnostics/debugging-with-symbols-and-sources.md#pdb-formats that discusses the PDB formats.

@BillWagner BillWagner added this to the Backlog milestone Aug 14, 2018
@EsaHeikkiPoutanen
Copy link

Azure function c# Visual studio 2017, debugging locally, fine, remote debugging: 'no symbols have been loaded...' crap when I try to set up break, point ! Have tried various debug options with no results..
enfuriating !!!

@EsaHeikkiPoutanen
Copy link

Oh, and this only happens when using V2 fuctions and .net code, V1 functions, remote debugging works fine

Copy link
Contributor

This documentation is still out of sync because the newly added options such as embedded, portable are not updated while there are external documentation that describes this. It will be good to capture the same information in this page as well

@ericsampson
Copy link

@IEvangelist this page is massively out of date and wrong.

@ericsampson
Copy link

@dotnet/docs this is still valid and important to update. Should be not hard.

@ericsampson
Copy link

@BillWagner I don't seem to be able to reopen this as the bot message suggests, I must not have the rights.

@akoeplinger
Copy link
Member

akoeplinger commented Jan 25, 2021

Yeah only repo collaborators can reopen issues, that is a longstanding issue with GitHub: isaacs/github#583

I also think this is still needed so reopening (note that I'm not a member of dotnet/docs but looks like every dotnet organization user can do it).

@akoeplinger akoeplinger reopened this Jan 25, 2021
@akoeplinger akoeplinger removed the won't fix Issues that were closed as part of automated backlog grooming label Jan 25, 2021
@BillWagner
Copy link
Member

BillWagner commented Jan 25, 2021

@dotnet/docs should be sufficient to tag the team.

It looks like the markdown to add is the following:

[@dotnet/docs](https://github.com/orgs/dotnet/teams/docs)

@sharwell
Copy link
Member

sharwell commented Jan 25, 2021

@BillWagner The markdown to tag the team is @dotnet/docs, but only members of the org can use it. Users outside the org can mention people, but cannot mention groups.

@ericsampson
Copy link

yeah unfortunately I already tried to tag the group. Really unfortunate that externals like regular devs can't tag as described in the bot note.

@BillWagner
Copy link
Member

@ericsampson

Really unfortunate that externals like regular devs can't tag as described in the bot note.

Yeah, that's annoying. I've sent email to my team and we're watching closely for comments.

@akoeplinger
Copy link
Member

#22797 didn't fully fix the original issue since https://docs.microsoft.com/en-us/dotnet/csharp/language-reference/compiler-options/code-generation#debugtype still only mentions pdbonly/full and misses the portable and embedded options, even though portable is the default and recommended option for new .NET projects now.

Reopening, @BillWagner not sure if this will put it in the correct GitHub tracking state so please fix if it's wrong :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
doc-bug Problem with the content; needs to be fixed [org][type][category] dotnet-csharp/svc errors-warnings/subsvc Pri2
Projects
None yet