From: Andrew Burgess <aburgess@redhat.com>
To: "Gerlicher, Klaus" <klaus.gerlicher@intel.com>,
Kevin Buettner <kevinb@redhat.com>, Tom Tromey <tom@tromey.com>,
Pedro Alves <pedro@palves.net>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: RE: [PATCH 1/1] gdb, breakpoint: use breakpoint_debug_printf
Date: Thu, 17 Jul 2025 18:02:22 +0100 [thread overview]
Message-ID: <87jz46lpi9.fsf@redhat.com> (raw)
In-Reply-To: <DM3PPFD7E67F0365072DAA454401623D2C7E848A@DM3PPFD7E67F036.namprd11.prod.outlook.com>
"Gerlicher, Klaus" <klaus.gerlicher@intel.com> writes:
> Hi,
>
> Thanks for the quick response. I see, we need to include Pedro then I guess. It's
> not terribly important, I was just adding some things to breakpoint for our purposes
> and I hit this oddity.
For what it's worth I agree with Tom and Simon that these should not be
changed to breakpoint debug. In my head the debug printing has always
been based on functionality rather than file, and these do seem to be
more about inferior control than breakpoint creation/management.
Thanks,
Andrew
>
> +Pedro
>
> Thanks
> Klaus
>
>> -----Original Message-----
>> From: Kevin Buettner <kevinb@redhat.com>
>> Sent: Thursday, July 10, 2025 4:59 AM
>> To: Tom Tromey <tom@tromey.com>
>> Cc: gdb-patches@sourceware.org; Gerlicher, Klaus
>> <klaus.gerlicher@intel.com>
>> Subject: Re: [PATCH 1/1] gdb, breakpoint: use breakpoint_debug_printf
>>
>> On Wed, 09 Jul 2025 13:21:14 -0600
>> Tom Tromey <tom@tromey.com> wrote:
>>
>> > >>>>> "Klaus" == Klaus Gerlicher <klaus.gerlicher@intel.com> writes:
>> >
>> > Klaus> Some debug prints in breakpoint.c are using
>> > Klaus> infrun_debug_printf (). This does not seem to be the
>> > Klaus> right debug print macro.
>> >
>> > Klaus> Use breakpoint_debug_printf () exclusively in this file.
>> >
>> > I am not so sure about this. It seems to me that some of these may
>> > mostly of interest when infrun debugging is enabled. For example:
>> >
>> > Klaus> - infrun_debug_printf ("incorrect thread or task, not
>> > Klaus> stopping");
>> > Klaus> + breakpoint_debug_printf ("incorrect thread or task, not
>> > Klaus> stopping");
>> >
>> > This kind of thing is a decision impacting infrun decisions.
>>
>> Hmm, good point. I rescind my approval.
>>
>> Kevin
>
> Intel Deutschland GmbH
> Registered Address: Am Campeon 10, 85579 Neubiberg, Germany
> Tel: +49 89 99 8853-0, www.intel.de
> Managing Directors: Sean Fennelly, Jeffrey Schneiderman, Tiffany Doon Silva
> Chairperson of the Supervisory Board: Nicole Lau
> Registered Office: Munich
> Commercial Register: Amtsgericht Muenchen HRB 186928
prev parent reply other threads:[~2025-07-17 17:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-08 13:21 Klaus Gerlicher
2025-07-08 15:46 ` Kevin Buettner
2025-07-09 19:21 ` Tom Tromey
2025-07-10 2:58 ` Kevin Buettner
2025-07-10 8:43 ` Gerlicher, Klaus
2025-07-11 15:22 ` Simon Marchi
2025-07-17 17:02 ` Andrew Burgess [this message]
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=87jz46lpi9.fsf@redhat.com \
--to=aburgess@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=kevinb@redhat.com \
--cc=klaus.gerlicher@intel.com \
--cc=pedro@palves.net \
--cc=tom@tromey.com \
/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