Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: bauerman@br.ibm.com (Thiago Jung Bauermann)
Cc: gdb-patches@sourceware.org (gdb-patches ml)
Subject: Re: [RFA] Implement support for PowerPC BookE ranged breakpoints
Date: Wed, 16 Mar 2011 18:00:00 -0000	[thread overview]
Message-ID: <201103161745.p2GHjiV1032056@d06av02.portsmouth.uk.ibm.com> (raw)
In-Reply-To: <1300242390.5316.11.camel@hactar> from "Thiago Jung Bauermann" at Mar 15, 2011 11:26:30 PM

Thiago Jung Bauermann wrote:
> On Mon, 2011-03-14 at 21:01 +0100, Ulrich Weigand wrote:
> > Thus I'd prefer to not duplicate the logic in ui_out_field_core_addr,
> > but rather just call it twice (using a temporary stream).
> 
> ui_out_field_core_addr takes a struct ui_out, so I don't know how to
> make it print to a temporary stream so I can call it twice from
> print_one_detail_ranged_breakpoint without having to specify a different
> field name in each call. What about putting the address-printing logic
> in a function which uses a temporary stream, then make both
> ui_out_field_core_addr and print_one_detail_ranged_breakpoint use it?
> The patch below implements the idea.

OK, I like that ...  Maybe it would be even better to move the new
routine into utils.c next to paddress, the only other routine to
format addresses at the moment?

This could e.g. take the form of a routine

  const char *
  paddress_padded (struct gdbarch *gdbarch, CORE_ADDR addr)

which returns a string just like paddress, but padded to at least 8
or 16 characters, depending on the address size.

ui_out_field_core_addr (and print_one_detail_ranged_breakpoint) could
then just use this to print into a temporary stream ...

Thanks,
Ulrich

-- 
  Dr. Ulrich Weigand
  GNU Toolchain for Linux on System z and Cell BE
  Ulrich.Weigand@de.ibm.com


  reply	other threads:[~2011-03-16 17:45 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-28  1:54 Thiago Jung Bauermann
2011-01-28  9:39 ` Eli Zaretskii
2011-01-31 19:07   ` Thiago Jung Bauermann
2011-01-31 20:39     ` Eli Zaretskii
2011-02-17 15:49 ` Ulrich Weigand
2011-02-23 20:50   ` Thiago Jung Bauermann
2011-02-24 20:45     ` [rfc] More intelligent indenting of multi-line table entries (Re: [RFA] Implement support for PowerPC BookE ranged breakpoints) Ulrich Weigand
2011-02-25 14:46       ` Pedro Alves
2011-02-28 15:33         ` [rfc] More intelligent indenting of multi-line table entries (Re: [RFA] Implement support for PowerPC BookE ranged breakpoin Ulrich Weigand
2011-02-28 16:34           ` [commit] Remove unused parameter (Re: [rfc] More intelligent indenting of multi-line table entries) Ulrich Weigand
2011-02-25 15:33       ` [rfc] More intelligent indenting of multi-line table entries (Re: [RFA] Implement support for PowerPC BookE ranged breakpoints) Thiago Jung Bauermann
2011-02-28 17:08     ` [RFA] Implement support for PowerPC BookE ranged breakpoints Ulrich Weigand
2011-03-12  2:03       ` Thiago Jung Bauermann
2011-03-12 16:44         ` Thiago Jung Bauermann
2011-03-14 20:50           ` Ulrich Weigand
2011-03-16  6:07             ` Thiago Jung Bauermann
2011-03-16 18:00               ` Ulrich Weigand [this message]
2011-03-14 21:02         ` Ulrich Weigand
2011-03-28 16:50           ` Thiago Jung Bauermann
2011-03-29 13:10             ` Ulrich Weigand
2011-03-31 15:41               ` Thiago Jung Bauermann
2011-03-31 16:04                 ` Thiago Jung Bauermann

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=201103161745.p2GHjiV1032056@d06av02.portsmouth.uk.ibm.com \
    --to=uweigand@de.ibm.com \
    --cc=bauerman@br.ibm.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