Community
Participate
Working Groups
We currently set tracepoints using the 'trace' CLI command. CLI commands do not support the --thread-group flag. Therefore, when we run multi-process and set a tracepoint, it does not get set for each process, but gets set multiple times for the current process in focus. We can fix this by using the the MI command -break-insert -a for tracepoints which was introduced in GDB 7.1. We can also fix this more generally by fixing bug 265673
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.
