From: Bernd Edlinger <bernd.edlinger@hotmail.de>
To: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Cc: Tom Tromey <tom@tromey.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Fix gdb crash due to SIGPIPE when the compile command fails
Date: Mon, 14 Jun 2021 14:57:00 +0200 [thread overview]
Message-ID: <AS8PR10MB4712AE29E966243F943BAB3AE4319@AS8PR10MB4712.EURPRD10.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <ydd5yygd675.fsf@CeBiTec.Uni-Bielefeld.DE>
Hi Rainer,
On 6/14/21 1:41 PM, Rainer Orth wrote:
> Hi Bernd,
>
>> On 6/4/21 3:39 PM, Tom Tromey wrote:
>>>>>>>> "Bernd" == Bernd Edlinger <bernd.edlinger@hotmail.de> writes:
>>>
>>> Bernd> I believe it is right to avoid the SIGPIPE before calling the plugin,
>>> Bernd> instead of doing that in gcc-trunk, since we don't know which version
>>> Bernd> we will be calling, and all versions I tried have failed like this.
>>>
>>> That seems fine, but I think it would be better to install the handler
>>> just when working with the plugin, and then uninstall it afterward, sort
>>> of like what class scoped_ignore_sigttou does.
>>>
>>
>> Okay, done, that works for me.
>>
>> Is this OK?
>
> this patch broke the Solaris build:
>
> /vol/src/gnu/gdb/hg/master/dist/gdb/compile/compile.c:659:3: error: ‘sighandler_t’ does not name a type; did you mean ‘sa_handler’?
> 659 | sighandler_t m_osigpipe = NULL;
> | ^~~~~~~~~~~~
> | sa_handler
> /vol/src/gnu/gdb/hg/master/dist/gdb/compile/compile.c: In constructor ‘scoped_ignore_sigpipe::scoped_ignore_sigpipe()’:
> /vol/src/gnu/gdb/hg/master/dist/gdb/compile/compile.c:644:5: error: ‘m_osigpipe’ was not declared in this scope
> 644 | m_osigpipe = signal (SIGPIPE, SIG_IGN);
> | ^~~~~~~~~~
> /vol/src/gnu/gdb/hg/master/dist/gdb/compile/compile.c:644:18: error: ‘signal’ was not declared in this scope; did you mean ‘sigval’?
> 644 | m_osigpipe = signal (SIGPIPE, SIG_IGN);
> | ^~~~~~
> | sigval
> /vol/src/gnu/gdb/hg/master/dist/gdb/compile/compile.c: In destructor ‘scoped_ignore_sigpipe::~scoped_ignore_sigpipe()’:
> /vol/src/gnu/gdb/hg/master/dist/gdb/compile/compile.c:651:22: error: ‘m_osigpipe’ was not declared in this scope
> 651 | signal (SIGPIPE, m_osigpipe);
> | ^~~~~~~~~~
> /vol/src/gnu/gdb/hg/master/dist/gdb/compile/compile.c:651:5: error: ‘signal’ was not declared in this scope; did you mean ‘sigval’?
> 651 | signal (SIGPIPE, m_osigpipe);
> | ^~~~~~
> | sigval
>
> and I have a very hard time deciding where <signal.h> needs to be
> included given the enormous range of headers included by compile.c.
>
Oh, I see, looks like it did only work by chance.
Maybe just include it after all other headers:
From 6c6d25339460df2ad6eade17cc47a5e472208cc0 Mon Sep 17 00:00:00 2001
From: Bernd Edlinger <bernd.edlinger@hotmail.de>
Date: Mon, 14 Jun 2021 14:49:21 +0200
Subject: [PATCH] Include missing header signal.h
2021-06-14 Bernd Edlinger <bernd.edlinger@hotmail.de>
* compile/compile.c: Include missing header signal.h.
---
gdb/compile/compile.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/gdb/compile/compile.c b/gdb/compile/compile.c
index 8247fc4..abbb72a 100644
--- a/gdb/compile/compile.c
+++ b/gdb/compile/compile.c
@@ -43,6 +43,7 @@
#include "gdbsupport/gdb_optional.h"
#include "gdbsupport/gdb_unlinker.h"
#include "gdbsupport/pathstuff.h"
+#include <signal.h>
^L
--
1.9.1
I guess, I'll commit it as obvious, unless someone objects.
Thanks
Bernd.
next prev parent reply other threads:[~2021-06-14 12:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-02 17:31 Bernd Edlinger
2021-06-02 18:21 ` Tom Tromey
2021-06-02 22:19 ` Christian Biesinger
2021-06-03 5:45 ` Bernd Edlinger
2021-06-04 13:39 ` Tom Tromey
2021-06-05 11:44 ` Bernd Edlinger
2021-06-05 12:04 ` Andrew Burgess
2021-06-05 12:27 ` Bernd Edlinger
2021-06-05 14:04 ` Tom Tromey
2021-06-14 11:41 ` Rainer Orth
2021-06-14 12:57 ` Bernd Edlinger [this message]
2021-06-14 12:59 ` Rainer Orth
2021-06-14 14:36 ` Bernd Edlinger
2021-06-14 14:39 ` Rainer Orth
2021-06-14 15:07 ` Tom Tromey
2021-06-15 11:10 ` Rainer Orth
2021-06-14 15:04 ` Tom Tromey
2021-06-14 23:35 ` Pedro Alves
2021-06-15 5:14 ` Bernd Edlinger
2021-06-15 11:16 ` Pedro Alves
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=AS8PR10MB4712AE29E966243F943BAB3AE4319@AS8PR10MB4712.EURPRD10.PROD.OUTLOOK.COM \
--to=bernd.edlinger@hotmail.de \
--cc=gdb-patches@sourceware.org \
--cc=ro@CeBiTec.Uni-Bielefeld.DE \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).