| Summary: | [tracepoints][multi-process] A tracepoint is not being set on the right process when using multi-process | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Tools] CDT | Reporter: | Marc Khouzam <marc.khouzam> | ||||||
| Component: | cdt-debug-dsf-gdb | Assignee: | Marc Khouzam <marc.khouzam> | ||||||
| Status: | RESOLVED FIXED | QA Contact: | Marc Khouzam <marc.khouzam> | ||||||
| Severity: | normal | ||||||||
| Priority: | P3 | CC: | cdtdoug, pawel.1.piech | ||||||
| Version: | 8.0 | Flags: | pawel.1.piech:
review+
|
||||||
| Target Milestone: | 8.1.0 | ||||||||
| Hardware: | PC | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Attachments: |
|
||||||||
|
Description
Marc Khouzam
Created attachment 196807 [details]
Fix to use -break-insert -a for tracepoints
-break-insert -a was actually introduce in GDB 7.2
This patch makes use of it.
Created attachment 198677 [details]
Git patch for fix
This is the patch I committed to master. It uses MI to set tracepoints, starting with GDB 7.2, which is where the MI command (-break-insert -a) become available.
Pawel, can your review? Note that I didn't commit to the 8_0 branch because I added a new class, which I don't believed I'm allowed to add to a maintenance branch.
> Note that I didn't commit to the 8_0 branch because I added a new class, which
> I don't believed I'm allowed to add to a maintenance branch.
What if I create the new class in an internal package for the 8_0 branch? This is really a bug fix and not a feature, so it should be in the 8_0 branch.
I'm not too familiar with gdb tracepoints but the patch looks kosher to me. (In reply to comment #4) > What if I create the new class in an internal package for the 8_0 branch? This > is really a bug fix and not a feature, so it should be in the 8_0 branch. Sure, I think it's a reasonable workaround for the API tooling. |