This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug breakpoints/16466] -break-insert and -dprintf-insert do not remember a specified thread for a pending breakpoint
- From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Tue, 24 Mar 2015 12:45:15 +0000
- Subject: [Bug breakpoints/16466] -break-insert and -dprintf-insert do not remember a specified thread for a pending breakpoint
- Auto-submitted: auto-generated
- References: <bug-16466-4717 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=16466
--- Comment #2 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Antoine Tremblay <hexa@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=15630549010233e9d0f0b1971d27e121cd74bdd0
commit 15630549010233e9d0f0b1971d27e121cd74bdd0
Author: Antoine Tremblay <antoine.tremblay@ericsson.com>
Date: Thu Feb 19 15:23:34 2015 -0500
Fix breakpoint thread condition missing with mi and a pending breakpoint.
When setting a pending breakpoint with a thread condition while using
the mi interface, the thread condition would be lost by gdb when the
breakpoint
was resolved.
This patch fixes this behavior by setting the thread condition properly in
the
mi case.
Also, this patch modifies the mi-pending test case to test for this issue
and
removes some unneeded code in the testcase and dependency on stdio.
gdb/Changelog:
PR breakpoints/16466
* breakpoint.c (create_breakpoint): Set thread on breakpoint struct.
gdb/testsuite/ChangeLog:
PR breakpoints/16466
* gdb.mi/Makefile.in: Add mi-pendshr2.sl to cleanup.
* gdb.mi/mi-pending.c (thread_func): New function.
(int main): Add threading support required.
* gdb.mi/mi-pending.exp: Add tests for this issue.
* gdb.mi/mi-pendshr.c (pendfunc1): Remove stdio dependency.
(pendfunc2): Remove stdio dependency.
* gdb.mi/mi-pendshr2.c: New file.
--
You are receiving this mail because:
You are on the CC list for the bug.