Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <yao@codesourcery.com>
To: <gdb-patches@sourceware.org>
Subject: [PATCH 0/3] dprintf tweaks
Date: Wed, 12 Dec 2012 04:13:00 -0000	[thread overview]
Message-ID: <1355285581-28889-1-git-send-email-yao@codesourcery.com> (raw)

Hi,
I happen to see that a block of code about dprintf in
print_one_breakpoint_location is dead, and patch 2/3 is
to remove the dead block.  Patch 1/3 is to test the output
of 'info breakpoints' for dprintf in different dprint-style.

The whole series are tested on x86_linux with native and
gdbserver board file.

  Test of breakpoint output for dprintf
  Remove dead code for dprintf.
  Assert 'printf_line' is non-null.

 gdb/breakpoint.c                               |   49 ++++++++++--------------
 gdb/testsuite/gdb.base/dprintf.exp             |   13 ++++++
 gdb/testsuite/gdb.mi/mi-breakpoint-changed.exp |    2 +-
 3 files changed, 34 insertions(+), 30 deletions(-)

-- 
1.7.7.6


             reply	other threads:[~2012-12-12  4:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-12  4:13 Yao Qi [this message]
2012-12-12  4:13 ` [PATCH 3/3] Assert 'printf_line' is non-null Yao Qi
2013-01-09 21:43   ` Tom Tromey
2012-12-12  4:13 ` [PATCH 2/3] Remove dead code for dprintf Yao Qi
2013-01-09 20:45   ` Tom Tromey
2012-12-12  4:13 ` [PATCH 1/3] Test of breakpoint output " Yao Qi
2013-01-09 20:35   ` Tom Tromey
2013-01-10  5:43     ` Joel Brobecker
2013-01-10 14:53       ` Yao Qi
2013-01-10 14:55         ` Tom Tromey
2013-01-11 15:22         ` [obv] Fix new FAIL on 64-bit targets [Re: [PATCH 1/3] Test of breakpoint output for dprintf] Jan Kratochvil
2013-01-07 14:16 ` [ping]: [PATCH 0/3] dprintf tweaks Yao Qi

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=1355285581-28889-1-git-send-email-yao@codesourcery.com \
    --to=yao@codesourcery.com \
    --cc=gdb-patches@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