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: | Allow expressions from breakpoint context in the Print Text field of breakpoint customizer. | ||
---|---|---|---|
Product: | debugger | Reporter: | _ sandipchitale <sandipchitale> |
Component: | Code | Assignee: | issues@debugger <issues> |
Status: | CLOSED WORKSFORME | ||
Severity: | blocker | ||
Priority: | P3 | ||
Version: | 5.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | ENHANCEMENT | Exception Reporter: |
Description
_ sandipchitale
2005-05-11 18:48:14 UTC
Not sure what you mean. In current version it is possible to add an expression to breakpoint "Print Text", e.g.: {=a[10] + b} Let me know whether this is answer to your RFE. Thanks! I only see the following in the Print Text: Breakpoint hit at line {lineNumber} in class {className} by thread {threadName}. All of {lineNumber}, {className} and {threadName} looked like some special tokens provided by the debugger and not expressions from user program. That is why I did not think it was possible to add expresseions using variables, parameters and fields of breakpoint context in the user's program. May be a label or a tooltip could be added to tell the user that they can add any expression using variables, parameters and fields of breakpoint context. Can you please explain the syntax: {=a[10] + b} Won't the tokens - {lineNumber}, {className} and {threadName} conflict with the user's variable, parameter or fiedl names? Or is the '{...}' vs '{=...}' syntax distiguishes those? I better go an RTFineM. Syntax is like {=EXPRESSION} where EXPRESSION is expression to be evaluate ;-) 1. I could not find the info about {=EXPRESSION} in the Online Help. How will the user's discover the functionality? 2. What other special tokens similar to {lineNumber}, {className} and {threadName} are available? There are following tokens available: {threadName} {className} {methodName} {lineNumber} {=EXPRESSION} We will check the documentation, thanks for info. Verified ... and Closing all issues resolved into NetBeans 6.7 and earlier. |