Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Guinevere Larsen <guinevere@redhat.com>
To: "Aktemur, Tankut Baris" <tankut.baris.aktemur@intel.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	Tom Tromey <tom@tromey.com>
Subject: Re: [PATCH v5] gdb: Introduce RAII signal handler setter
Date: Wed, 15 Apr 2026 10:16:45 -0300	[thread overview]
Message-ID: <2c613de1-5671-4f20-95a8-e43413dd808e@redhat.com> (raw)
In-Reply-To: <DM4PR11MB7303F64A5A87EC77DF006E71C4222@DM4PR11MB7303.namprd11.prod.outlook.com>

On 4/15/26 10:10 AM, Aktemur, Tankut Baris wrote:
> Hi Guinevere,
>
> On Friday, November 22, 2024 6:51 PM, Guinevere Larsen wrote:
>> On 11/22/24 12:55 PM, Tom Tromey wrote:
>>>>>>>> "Guinevere" == Guinevere Larsen <guinevere@redhat.com> writes:
>>> Guinevere> +#if defined (HAVE_SIGACTION)
>>> Guinevere> +  struct sigaction m_prev_handler;
>>> Guinevere> +#else
>>> Guinevere> +  typedef sighandler_t m_prev_handler;
>>> Guinevere> +#endif
>>>
>>> That #else branch looks wrong, I would guess s/typedef//
>> gah! thanks, copy-paste issues. will fix
>>> gnulib says sigaction isn't on mingw, so maybe a mingw cross-hosted
>>> build would show the problem.
>> I have un-defined the macro and tested.
> Could it be that the local experiment above sneaked into
> gdbsupport/scoped_signal_handler.h?  In that file there is
>
>    #undef HAVE_SIGACTION
>
> which seems to clear the macro unintentionally.
oops, yes, it probably sneaked in. The file definitely was not supposed 
to be unsetting the macro.
>
> Regards,
> -Baris
>
>
> Intel Deutschland GmbH
> Registered Address: Dornacher Strasse 1, 85622 Feldkirchen, Germany
> Tel: +49 89 991 430, www.intel.de
> Managing Directors: Harry Demas, Jeffrey Schneiderman, Yin Chong Sorrell
> Chairperson of the Supervisory Board: Nicole Lau
> Registered Seat: Munich
> Commercial Register: Amtsgericht Muenchen HRB 186928
>

-- 
Cheers,
Guinevere Larsen
It/she


      reply	other threads:[~2026-04-15 13:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-18 19:57 Guinevere Larsen
2024-11-22 15:55 ` Tom Tromey
2024-11-22 17:50   ` Guinevere Larsen
2024-11-22 18:46     ` Tom Tromey
2024-11-22 20:38       ` Guinevere Larsen
2026-04-15 13:10     ` Aktemur, Tankut Baris
2026-04-15 13:16       ` Guinevere Larsen [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=2c613de1-5671-4f20-95a8-e43413dd808e@redhat.com \
    --to=guinevere@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tankut.baris.aktemur@intel.com \
    --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