This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] Fix 19548: Breakpoint re-set inserts breakpoints when it shouldn't
- From: Pedro Alves <palves at redhat dot com>
- To: GDB Patches <gdb-patches at sourceware dot org>
- Date: Tue, 09 Feb 2016 12:23:47 +0000
- Subject: Re: [PATCH] Fix 19548: Breakpoint re-set inserts breakpoints when it shouldn't
- Authentication-results: sourceware.org; auth=none
- References: <1454346246-28564-1-git-send-email-palves at redhat dot com>
I pushed this in now, with a tiny change to a comment:
On 02/01/2016 05:04 PM, Pedro Alves wrote:
> - # On a buggy GDB, with always-inserted on, we'd see:
> + # Set a second breakpoint (whose original address also ends up
> + # unmmapped after the exec), for PR 19548.
> + gdb_test "break some_function" "Breakpoint .*"
> +
> + # PR17431: with always-inserted on, we'd see:
> # (gdb) continue
> # Continuing.
> # Warning:
> # Cannot insert breakpoint 1.
> # Cannot access memory at address 0x10000ff
> - gdb_test "continue" "Breakpoint 1, main.*" "continue across exec"
> +
> + # PR 19548: with more than one breakpoint, we'd see:
> + # (gdb) continue
> + # Continuing.
> + # process 17227 is executing new program: (...)/execl-update-breakpoints2
Looking at the diff again, I noticed this "17227" here looks confusingly similar
to the PRs listed, so I replaced it with "(...)".
Thanks,
Pedro Alves