This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [RFA v3] enable/disable sub breakpoint range


Le 10/3/17 à 6:02 PM, Pedro Alves a écrit :
We'd do the same to breakpoint commands, i.e., commands that take
an breakpoint/location list would xref the description of breakpoint
lists.

See commit 5d5658a1d3c3 ("Per-inferior/Inferior-qualified thread IDs")
for how that looked like before support for '*' ranges was added.

(And now I wonder whether it'd make sense to model the breakpoint
number parsing on a simplified version of the thread ID number
parsing.  See gdb/tid-parse.h / tid_range_parser.)

Thanks,
Pedro Alves >

We have several ways for achieving this, especially when taking the C++ization of the code in account. What do you think would be the best approach:

- commit patch I've done as a first step, then propose a new patch including '.*' support ?

- write a breakpoint location range parser similar to the tid (for thread) one in pure C style including the '.*' support ? In that case what about the C++ization ? Would it be done in the future ?

- Change the patch I've proposed to integrate '.*' support in the new C++ style function I wrote ?

Something else ?

Regards.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]