This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | selecting expression for debugger tooltip cause program core dump when step out from method | ||
---|---|---|---|
Product: | cnd | Reporter: | Vladimir Voskresensky <vv159170> |
Component: | Debugger | Assignee: | Maria Tishkova <mromashova> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | P1 | ||
Version: | Dev | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: |
suggested_fix
proposed fix (-var-delete invoked for closed pinned tooltip) |
Description
Vladimir Voskresensky
2017-03-01 16:01:17 UTC
suggested fix is attached. Please evaluate if it works for you Created attachment 163746 [details]
suggested_fix
please evaluate and let me know if the problem is gone
Interesting effect: Tooltip doesn't show value if selected expression has function call (fun_call) in which I have breakpoint Displayed like: fun_call(val)= I tried multiple times... After that the next step stopped me multiple times in fun_call. Looks like we hit breakpoints when evaluate expression when I removed breakpoint from inside fun_call Displayed like: fun_call(val)=1234 I recommend to see CR 19720112 too. Vladimir, please attach gdb log. When you are talking about function expression evaluation do you mean that it worked before this patch? And we do not hit breakpoint by intention when evaluate function evaluation maybe GDB does? (In reply to soldatov from comment #5) > I recommend to see CR 19720112 too. Valera, What you refer to is dbx bug. The problems the bug is filed is in GDB (In reply to Vladimir Voskresensky from comment #4) > when I removed breakpoint from inside fun_call > Displayed like: fun_call(val)=1234 Vova, what about the problem this bug was filed about. Core dump and slow down. Have you checked if the patch helps. ==Masha (In reply to Maria Tishkova from comment #8) > (In reply to Vladimir Voskresensky from comment #4) > > when I removed breakpoint from inside fun_call > > Displayed like: fun_call(val)=1234 > > Vova, > > what about the problem this bug was filed about. Core dump and slow down. > Have you checked if the patch helps. > > ==Masha Evaluating... Created attachment 163747 [details]
proposed fix (-var-delete invoked for closed pinned tooltip)
(In reply to Maria Tishkova from comment #6) > Vladimir, please attach gdb log. > When you are talking about function expression evaluation do you mean that > it worked before this patch? Probably not related to the patch. > And we do not hit breakpoint by intention when evaluate function evaluation > maybe GDB does? I don't know. I will file a separate bug with a log (In reply to Maria Tishkova from comment #10) > Created attachment 163747 [details] > proposed fix (-var-delete invoked for closed pinned tooltip) I hope System.out.println is not required :-) > What you refer to is dbx bug. The problems the bug is filed is in GDB
It is not a DBX bug. Function call is very dangerous operation if we speak about native languages (C, C++ and other). Therefore IDE returns address only. If user calls function or method He/She understand risk, debugger can fails in any moment.
(In reply to Vladimir Voskresensky from comment #11) > (In reply to Maria Tishkova from comment #6) > > Vladimir, please attach gdb log. > > When you are talking about function expression evaluation do you mean that > > it worked before this patch? > Probably not related to the patch. > > > And we do not hit breakpoint by intention when evaluate function evaluation > > maybe GDB does? > I don't know. I will file a separate bug with a log https://netbeans.org/bugzilla/show_bug.cgi?id=269968 (In reply to soldatov from comment #13) > > What you refer to is dbx bug. The problems the bug is filed is in GDB > It is not a DBX bug. Function call is very dangerous operation if we speak > about native languages (C, C++ and other). Therefore IDE returns address > only. If user calls function or method He/She understand risk, debugger can > fails in any moment. As a user I find it very useful that instead of step-into I can evaluate expression in tooltip. Yes, I understand the risk, but I known better when I call const-methods. Simple Usecase: // Either in a function body compound statement, or a function-try-block. switch (CheckFallThrough(AC)) { case UnknownFallThrough: break; case ... .... break; case ... .... break; fixed in enum/release82 - should be transplanted into the trunk and releases(release82) changeset: 314364:1df91d650025 branch: release82 user: Maria Dalmatova <mromashova@netbeans.org> date: Sun Mar 05 21:01:52 2017 +0300 summary: fixed bz#269959 - selecting expression for debugger tooltip cause program core dump when step out from method Integrated into 'main-silver', will be available in build *201703070002* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-silver/rev/71d47fcf768e User: Maria Dalmatova <mromashova@netbeans.org> Log: fixed bz#269959 - selecting expression for debugger tooltip cause program core dump when step out from method (transplanted from 1df91d650025751971cadc4aa88f5dd8ae4d5378) https://netbeans.org/bugzilla/show_bug.cgi?id=269959 Changesets: http://hg.netbeans.org/releases/rev/1df91d650025 # fixed bz#269959 - selecting expression for debugger tooltip cause program core dump when step out from method |