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/15434] Dprintf uses a synchronous 'continue' even in non-stop mode
Date: Wed, 26 Jun 2013 02:32:00 -0000	[thread overview]
Message-ID: <bug-15434-4717-vH3sA4kmH8@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15434-4717@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=15434

--- Comment #9 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
CVSROOT:    /cvs/src
Module name:    src
Branch:     gdb_7_6-branch
Changes by:    teawater@sourceware.org    2013-06-26 02:31:58

Modified files:
    gdb            : breakpoint.c breakpoint.h 
    gdb/testsuite/gdb.base: dprintf.exp 
    gdb/testsuite/gdb.mi: mi-breakpoint-changed.exp 

Log message:
    2013-06-26  Yao Qi  <yao@codesourcery.com>
    Hui Zhu  <hui@codesourcery.com>
    Pedro Alves  <palves@redhat.com>

    PR breakpoints/15075
    PR breakpoints/15434
    * breakpoint.c (bpstat_stop_status): Call
    b->ops->after_condition_true.
    (update_dprintf_command_list): Don't append "continue" command
    to the command list of dprintf breakpoint.
    (base_breakpoint_after_condition_true): New function.
    (base_breakpoint_ops): Add base_breakpoint_after_condition_true.
    (dprintf_after_condition_true): New function.
    (initialize_breakpoint_ops): Set dprintf_after_condition_true.
    * breakpoint.h (breakpoint_ops): Add after_condition_true.

    2013-06-26  Yao Qi  <yao@codesourcery.com>
    Hui Zhu  <hui@codesourcery.com>
    Pedro Alves  <palves@redhat.com>

    PR breakpoints/15075
    PR breakpoints/15434
    * gdb.base/dprintf-next.c: New file.
    * gdb.base/dprintf-next.exp: New file.
    * gdb.base/dprintf-non-stop.c: New file.
    * gdb.base/dprintf-non-stop.exp: New file.
    * gdb.base/dprintf.exp: Don't check "continue" in the output
    of "info breakpoints".
    * gdb.mi/mi-breakpoint-changed.exp (test_insert_delete_modify):
    Don't check "continue" in script field.

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/src/gdb/breakpoint.c.diff?cvsroot=src&only_with_tag=gdb_7_6-branch&r1=1.745.2.6&r2=1.745.2.7
http://sourceware.org/cgi-bin/cvsweb.cgi/src/gdb/breakpoint.h.diff?cvsroot=src&only_with_tag=gdb_7_6-branch&r1=1.193&r2=1.193.2.1
http://sourceware.org/cgi-bin/cvsweb.cgi/src/gdb/testsuite/gdb.base/dprintf.exp.diff?cvsroot=src&only_with_tag=gdb_7_6-branch&r1=1.8.2.1&r2=1.8.2.2
http://sourceware.org/cgi-bin/cvsweb.cgi/src/gdb/testsuite/gdb.mi/mi-breakpoint-changed.exp.diff?cvsroot=src&only_with_tag=gdb_7_6-branch&r1=1.5&r2=1.5.2.1

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2013-06-26  2:32 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-06  2:25 [Bug breakpoints/15434] New: " marc.khouzam at ericsson dot com
2013-05-13  6:53 ` [Bug breakpoints/15434] " teawater at gmail dot com
2013-05-13  6:55 ` teawater at gmail dot com
2013-05-13  6:59 ` teawater at gmail dot com
2013-05-13  7:00 ` teawater at gmail dot com
2013-05-13 17:07 ` marc.khouzam at ericsson dot com
2013-05-13 17:12 ` marc.khouzam at ericsson dot com
2013-05-14 12:14 ` teawater at gmail dot com
2013-05-16  7:30 ` teawater at gmail dot com
2013-06-25 11:37 ` cvs-commit at gcc dot gnu.org
2013-06-25 11:42 ` teawater at gmail dot com
2013-06-26  2:32 ` cvs-commit at gcc dot gnu.org
2013-06-26  2:32 ` cvs-commit at gcc dot gnu.org [this message]
2014-01-10 16:01 ` marc.khouzam at ericsson dot com
2021-09-22 16:58 ` mervegunesli at aol dot com
2021-09-22 17:01 ` mark at klomp dot org

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-15434-4717-vH3sA4kmH8@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: link
Be 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).