From: Gary Benson <gbenson@redhat.com>
To: Simon Marchi <simark@simark.ca>
Cc: Joel Brobecker <brobecker@adacore.com>,
Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] gdb: add linux_nat_debug_printf macro
Date: Mon, 13 Jul 2020 15:56:22 +0100 [thread overview]
Message-ID: <20200713145622.GA25934@blade.nx> (raw)
In-Reply-To: <0ad0b987-cdca-a7a1-da8e-dafb5fac7e71@simark.ca>
Simon Marchi wrote:
> On 2020-07-13 10:32 a.m., Joel Brobecker wrote:
> > I skimmed through the patch, and it looked good to me.
> >
> > Thanks again for doing that. That's a nice improvement.
> >
> > Thinking out loud (and certainly not a suggestion or request that
> > you take care of the implementation): I'm wondering if we should be
> > thinking about generalizing this approach, somehow. For instance,
> > if we a function that took not just a func name, but also the name
> > of the unit:
> >
> > unit_debug_vprintf (const char *module_name, const char *func_name,
> > const char *fmt, ...)
> >
> > ... or perhaps more generally:
> >
> > unit_debug_vprintf (const char *label, const char *func_name,
> > const char *fmt, ...)
> >
> > ... then all modules would have to do to have consistent logging
> > is to define one macro.
>
> Yes, if people like the format I'd be open to changing other
> "modules" to use it, and having a generic function to ensure the
> same formatting is used everywhere would be the logical thing to do.
I like it :)
Cheers,
Gary
--
Gary Benson - he / him / his
Principal Software Engineer, Red Hat
next prev parent reply other threads:[~2020-07-13 14:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-02 19:30 [RFC PATCH] " Simon Marchi
2020-07-03 17:33 ` Joel Brobecker
2020-07-08 21:07 ` [PATCH] " Simon Marchi
2020-07-10 11:47 ` Gary Benson
2020-07-10 13:55 ` Simon Marchi
2020-07-10 14:23 ` Gary Benson
2020-07-13 14:32 ` Joel Brobecker
2020-07-13 14:38 ` Simon Marchi
2020-07-13 14:56 ` Gary Benson [this message]
2020-07-12 17:11 ` [RFC PATCH] " Tom Tromey
2020-08-19 2:56 ` Simon Marchi
2020-08-19 3:39 ` Simon Marchi
2020-08-19 3:44 ` Simon Marchi
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=20200713145622.GA25934@blade.nx \
--to=gbenson@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
/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