microsoft / microsoft/java-debug
[critical] Improve lambda breakpoints when using gradle build server
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 409
- Forks
- 204
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 4
Description
When using gradle build server, the lambda method name tends to change on large file which I'm not sure of the reason which I have not looked into Java Language Spec on how lambda method names are computed.
What was observed is the method name has the format classMethodName$lambda$#. This cause method name mismatches due to the JDT method name and JDI method name is different.
Contributor guide
No contributing guide indexed for this repository
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 by reproducing the lambda breakpoint mismatch with the Gradle build server and compare the JDT method name with the JDI method name. Investigate how lambda method names are computed for large files; done means breakpoints resolve despite the differing classMethodName$lambda$# names.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100