Steps to reproduce:
- create Welcome sample
- do step into project
- switch to disassembler
- set a breakpoint within "cout << "Welcome ...\n";" code
- finish debugger
- set a line BP at return statement
- run debugger
Result: Debugger stops at the Address BP but no annotation is shown. I would propose two possible solution:
1. Disassembler view should appear if process stops at Address BP
2. Special Address BP annotation should appear in source view if a user creates breakpoint in disassembler
IMO the second solution is better.
fixed in the changeset:
now when we stop at the address breakpoint we always open disassebly view
Fix failed in build 200812080201. Annotations disappear in a moment after setting.
One more inconvenience, Address breakpoints have absolute address in Breakpoints view whereas address in Disassembler
view is shown in relative manner (main+XXX).
fixed in the changeset:
*** Issue 155034 has been marked as a duplicate of this issue. ***
fix failed in build 200812120201 on all platforms
not included into build 200812120201 but verified with a new org-...-debugger-gdb.jar
verified in build 200812150201
it impossible to apply mentioned changeset(s) to release65_fixes [ref1] branch because a lot of non-this IZ related
changes were made and other changesets pushed into main [ref2] repository between release65_fixes branching time and
mentioned changeset(s) pushing time. Please provide cumulative changeset/ set of changesets applicable to
release65_fixes branch otherwise this fix will be skipped for current NB65 patch.
This problem is common for following IZs: 151761, 151610, 151577, 133134, 155487
It would be nice to have the fix in NB 6.5 patch
I think that the fix for the issue 155487:
fixes this issue as well (so there is no need to integrate the fix for this issue, only 155487) and it is a very simple
In what form should I provide the diff?
ups, differences are really too significant :(
verified in NB6.5 with provided jar files
> I think that the fix for the issue 155487:
> fixes this issue as well (so there is no need to integrate the fix
> for this issue, only 155487) and it is a very simple changeset.
> In what form should I provide the diff?
I took care of this with a patch to release65_fixes containing 155487 (and all
other 65fixes2-candidate issues).
Cumulative backport of fixes of IZ 151481(rebackport), 151577, 151610, 153473, 151640, 151761, 155487, 151631, 133134
provided by developer.
Backported into release65_fixes branch
verified in patch2
i need the library of c++ for netbeans now
please explain the priority escalation and describe your problem