public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug breakpoints/16465] -dprintf-insert does not store the string for pending dprintf Date: Fri, 12 Jun 2015 12:49:00 -0000 [thread overview] Message-ID: <bug-16465-4717-ZEYVr0zO6H@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-16465-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=16465 --- Comment #1 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=98aa42ee02c56378cecb737d01c27adca36bf48f commit 98aa42ee02c56378cecb737d01c27adca36bf48f Author: Antoine Tremblay <antoine.tremblay@ericsson.com> Date: Fri Jun 12 07:58:47 2015 -0400 Fix MI dprintf-insert not printing on a resolved pending location. This patch fixes the "Format string required" error when trying to print a dprintf on a now resolved, pending location when set via the MI interface even if the format string is entered correctly. This patch also adds a test case to check that issue called mi-dprintf-pending.exp. gdb/ChangeLog: PR breakpoints/16465 * breakpoint.c (create_breakpoint): Save extra_string for pending breakpoints. gdb/testsuite/ChangeLog: PR breakpoints/16465 * gdb.mi/mi-dprintf-pending.c: New file. * gdb.mi/mi-dprintf-pending.exp: New test. * gdb.mi/mi-dprintf-pendshr.c: New file. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2015-06-12 12:49 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-01-18 22:29 [Bug breakpoints/16465] New: " marc.khouzam at ericsson dot com 2014-01-18 22:30 ` [Bug breakpoints/16465] " marc.khouzam at ericsson dot com 2015-03-26 15:49 ` antoine.tremblay at ericsson dot com 2015-06-12 12:49 ` cvs-commit at gcc dot gnu.org [this message] 2015-06-12 12:53 ` antoine.tremblay at ericsson dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-16465-4717-ZEYVr0zO6H@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).