microsoft / microsoft/react-native-windows
Learn and Document Debugging RNW Apps in WinDbg
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 17.3k
- Forks
- 1.2k
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 33
Description
Expand on Chris' investigation of debugging a blank screen RNW app in Release via WinDbg.
Can we get a list of modules by name that have thrown exceptions? Can we get information on what those exceptions are, or where in the module's code they have taken place?
We should figure out how to get this information via WinDbg and add to the existing document we have on debugging RNW apps with WinDbg. This way developers can follow the steps to get more information.
Long term we could create a WinDbg extension that runs the steps automatically and spits out data.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the existing document on debugging RNW apps with WinDbg and Chris's investigation of the blank-screen Release app. Use WinDbg to determine how to list modules that threw exceptions and capture exception details or locations. Done means the document contains reproducible steps that developers can follow to obtain this information.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, react
- Domain
- devtools, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100