From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: gnulib m4/threadlib.m4 bug crashing package tests
Date: Thu, 25 Nov 2021 13:25:22 -0500 [thread overview]
Message-ID: <e8f954080e1983ab7d5491b1a2035f3a5980e669.camel@cygwin.com> (raw)
In-Reply-To: <04185622-bfb1-9828-a720-716fbdd2e0ab@cornell.edu>
On Thu, 2021-11-25 at 11:26 -0500, Ken Brown via Cygwin-apps wrote:
> On 9/29/2021 7:46 PM, Brian Inglis wrote:
> > There is a gnulib bug in threadlib.m4 from at least serial 29 to serial
> > 31 that incorrectly configures Cygwin support of weak references.
> >
> > This leads to SIGSEGV stack smashing crashes with no backtrace
> > @ 0x00000000100000000 or 0x0000000500000000 etc. normally during tests.
> >
> > Akim Demaille on bug-bison referred the issue to bug-gnulib where
> > Bruno Haible diagnosed and patched the problem to appear in
> > m4/threadlib.m4 serial 32:
> >
> > * m4/threadlib.m4 (gl_WEAK_SYMBOLS): Force a "guessing no" result on
> > Cygwin
> > https://lists.gnu.org/archive/html/bug-gnulib/2021-09/msg00068.html
> > [gl_cv_have_weak="guessing no"]
> >
> > The patch has now been applied to bison, wget, and wget2, and I have
> > attached my patches for the copies in those packages, in case anyone
> > else has this issue in their (mainly GNU) packages which may incorporate
> > by
> > inclusion recently updated gnulib m4 macros used in autotools builds.
>
> Thanks, Brian.
>
> I'm writing to reinforce this warning. I just spent 2 days trying to debug
> mysterious texinfo crashes that were caused by this bug. I could have saved
> a
> lot of time if I had remembered your email and had checked the gnulib
> version
> being used by texinfo.
>
> For anyone else who bumps into this, gdb and strace are of no use in
> debugging
> this crash. I finally thought to look at the stackdump file, and the second
> address from the top was in a gnulib file. That was the key clue.
Add gl_cv_have_weak=no to cygconf?
--
Yaakov
next prev parent reply other threads:[~2021-11-25 18:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-29 23:46 Brian Inglis
2021-11-25 16:26 ` Ken Brown
2021-11-25 18:25 ` Yaakov Selkowitz [this message]
2021-11-26 4:48 ` Brian Inglis
2021-11-26 13:08 ` Ken Brown
2021-11-26 17:34 ` Brian Inglis
2021-11-26 18:17 ` Ken Brown
2021-11-28 15:42 ` Achim Gratz
2021-11-28 15:56 ` Ken Brown
2021-11-28 16:33 ` Achim Gratz
2021-11-28 18:21 ` Ken Brown
2021-11-29 16:39 ` Achim Gratz
2021-12-08 18:49 ` Achim Gratz
2021-12-09 4:41 ` Brian Inglis
2021-11-28 16:23 ` Achim Gratz
2021-11-28 18:34 ` Brian Inglis
2021-11-29 17:38 ` Achim Gratz
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=e8f954080e1983ab7d5491b1a2035f3a5980e669.camel@cygwin.com \
--to=yselkowitz@cygwin.com \
--cc=cygwin-apps@cygwin.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).