| Summary: | [tracepoints] "Toggle Method Breakpoint" is not working as expected for tracepoints | ||
|---|---|---|---|
| Product: | [Tools] CDT | Reporter: | Nobody - feel free to take it <nobody> |
| Component: | cdt-debug | Assignee: | cdt-debug-inbox <cdt-debug-inbox> |
| Status: | NEW --- | QA Contact: | Jonah Graham <jonah> |
| Severity: | normal | ||
| Priority: | P3 | CC: | cdtdoug, marc.khouzam, pawel.1.piech |
| Version: | 8.0 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
|
Description
Nobody - feel free to take it
Did you also notice that for DSF-GDB, method breakpoints/tracepoints are not being set on the method, but are being set in GDB as line bp/tp? I just noticed this. For some reason, both the line and the method name are set as attributes which makes the bp service use the line number before it checks for a method name. Should I open a separate bug? (In reply to comment #1) > Did you also notice that for DSF-GDB, method breakpoints/tracepoints are not > being set on the method, but are being set in GDB as line bp/tp? > > I just noticed this. For some reason, both the line and the method name are > set as attributes which makes the bp service use the line number before it > checks for a method name. > As far as I know the line attribute is set to show the breakpoint in the editor. Can you check the breakpoint type before setting it? > Should I open a separate bug? I think it's better to open a separate bug. (In reply to comment #2) > (In reply to comment #1) > > Did you also notice that for DSF-GDB, method breakpoints/tracepoints are not > > being set on the method, but are being set in GDB as line bp/tp? > > > > I just noticed this. For some reason, both the line and the method name are > > set as attributes which makes the bp service use the line number before it > > checks for a method name. > > > > As far as I know the line attribute is set to show the breakpoint in the > editor. Can you check the breakpoint type before setting it? > > > Should I open a separate bug? > > I think it's better to open a separate bug. I opened Bug 336888 |