From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pl1-x62d.google.com (mail-pl1-x62d.google.com [IPv6:2607:f8b0:4864:20::62d]) by sourceware.org (Postfix) with ESMTPS id 539A93858C60 for ; Mon, 18 Oct 2021 19:01:39 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 539A93858C60 Received: by mail-pl1-x62d.google.com with SMTP id f21so11940590plb.3 for ; Mon, 18 Oct 2021 12:01:39 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to; bh=9p2MuzPL976+x7JxiRtwuQ7WDi8p6Xv1Ec1UV7WOYqY=; b=zFuIiOnUCaeRcowJyAXXeIjr4mb4m/lsWGLQceioWx7k00we8mbf1vQW0Y899ZeXw7 jIhLeCo6YkT9izGgzCW83mRQGbQtqJtz1QbzlGNnC4RODYU51YlMqTORNPLzNhu13YFp qokKz7A56qDo3HA2MznVVQIUlAO0lbtLDq3bhYWgkWfRMdX+2rXTC4abFkveGG5ylsV/ FYhoY/3vD11hhyqLgUhKx0fGadOLCQexPELyBfl2GZETfnUYWjQCQP0VivjY8r8COnkJ u8s8hNyHCJ1ttZqO+g/c5xQtL/I1aL5EqlyrEjyJH8mcoSBB2ZuOoHxH8Hyj6VMzN2mM aF9A== X-Gm-Message-State: AOAM530bvIjQOyGhNbKwTry4/eD1mExI81dkc3MEdYW6540nI2Epx8lm htIHTSdbIauQ/R3wosXj8v4hFJhaPv4tQeU= X-Google-Smtp-Source: ABdhPJy75W4qYUh6R2gwiR2mjNEl8748Xji0wR+V/MDFu6Q6hQZp/MP6w3j4Wk3st4uIigH+QRgewg== X-Received: by 2002:a17:90a:c594:: with SMTP id l20mr724218pjt.223.1634583698373; Mon, 18 Oct 2021 12:01:38 -0700 (PDT) Received: from takamaka.home ([184.69.131.86]) by smtp.gmail.com with ESMTPSA id e12sm14010085pgv.82.2021.10.18.12.01.37 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 18 Oct 2021 12:01:37 -0700 (PDT) Received: by takamaka.home (Postfix, from userid 1000) id E8D79808A4; Mon, 18 Oct 2021 12:01:36 -0700 (PDT) Date: Mon, 18 Oct 2021 12:01:36 -0700 From: Joel Brobecker To: Claudius =?iso-8859-1?Q?Schn=F6rr?= Cc: gdbadmin@sourceware.org, brobecker@adacore.com Subject: Re: Bugreport for binutils-gdb on cygwin Message-ID: <20211018190136.GD3549@adacore.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00, BODY_8BITS, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: gdbadmin@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdbadmin mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Oct 2021 19:01:41 -0000 Hello Claudius, > I write to you since I don't know where to submit a bugreport. > After trying to compile the insight gdb-frontent on cygwin > (git://sourceware.org/git/insight.git) the maintainer classified the > following issue to directly be addressed to binutils-gdb package: Personally, I unfortunately do not have much knowledge about cygwin (I know a little bit about MinGW-w64, but not cygwin). So I can't even tell whether cygwin implements the strsignal function or not. I think your best bet is if you can send the information you sent us to the GDB community at gdb-patches@sourceware.org instead. This is a good and easily understandable description of the issue you are facing, and perhaps there will be someone who knows enough about Cygwin to suggest a path forward, and in particular guide you towards fixing the problem and perhaps even submitting a patch. Another option is to perhaps contact the cygwin community to see if they have any information about that function. In particular, whether or not that function is available on cygwin platforms or not. You can try to report the issue on our bugzilla: https://sourceware.org/bugzilla/enter_bug.cgi?product=gdb > * platform: > o cygwin 64bit on Win-10 > o gcc (GCC) 11.2.0, g++ (GCC) 11.2.0 > > * commands submitted: > o git clone --recursive git://sourceware.org/git/binutils-gdb.git > o autoconf > o ./configure > o make > > * Error message: > o event-top.c: In function ‘void handle_fatal_signal(int)’: > event-top.c:893:18: error: ‘strsignal’ was not declared in this > scope; did you mean ‘strsigno’? >   893 |       sig_write (strsignal (sig)); > > * comment: > o strsignal() is declared in string.h. However, including it > doesn't work. > Then I inspected string.h on cygwin64 in /usr/include and found > this: > o #ifndef DEFS_H    /* Kludge to work around problem compiling in > gdb */ > char    *strsignal (int __signo); > #endif > o suggestion: undefining DEFS_H might be risky -> to be added at > line 55: > + #ifndef DEFS_H > #    include              /* for strsignal on > cygwin */ > #else > char *strsignal (int __signo);      /* see > /usr/include/string.h on cygwin */ > #endif > o then it compiles, however a library is missed now: > + x86_64-pc-cygwin/bin/ld: > event-top.o:.../insight/bundle/gdb/event-top.c:899: > undefined reference to `strsignal(int)' > collect2: error: ld returned 1 exit status > > Hope this helps somehow. > > Kind regards, > > Claudius > > -- Joel