This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: Regression for gdb.threads/fork-plus-threads.exp [Re: [PATCH 3/6] List inferiors/threads/pspaces in ascending order]
- From: Pedro Alves <palves at redhat dot com>
- To: Jan Kratochvil <jan dot kratochvil at redhat dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Wed, 13 Jan 2016 00:37:06 +0000
- Subject: Re: Regression for gdb.threads/fork-plus-threads.exp [Re: [PATCH 3/6] List inferiors/threads/pspaces in ascending order]
- Authentication-results: sourceware.org; auth=none
- References: <1445507944-9197-1-git-send-email-palves at redhat dot com> <1445507944-9197-4-git-send-email-palves at redhat dot com> <20160108203938 dot GA24397 at host1 dot jankratochvil dot net> <5693BEBC dot 4020404 at redhat dot com> <5694E1F9 dot 8070307 at redhat dot com>
On 01/12/2016 11:22 AM, Pedro Alves wrote:
> This is also yet another instance of breakpoint re-setting being too coarse [1]...
> If inferior 1 forked inferior 3, why would we need to re-set breakpoint locations
> of inferior 2? I think we can avoid revamping breakpoint re-set completely, by
> instead limiting re-sets to the program space that triggered it.
>
> [1] - https://sourceware.org/gdb/wiki/BreakpointReset
Patch posted here:
https://sourceware.org/ml/gdb-patches/2016-01/msg00246.html
Thanks,
Pedro Alves