|
From: | Brian Inglis |
Subject: | Re: bison segv under Cygwin 64 at fatal-signal.c:318 |
Date: | Mon, 13 Sep 2021 22:18:03 -0600 |
User-agent: | Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0 |
On 2021-09-13 17:19, Brian Inglis wrote:
On 2021-09-13 14:54, Brian Inglis wrote:On 2021-09-13 14:20, Akim Demaille wrote:Thanks for the very detailed bug report! Before trying to go further, could you please try this tarball, which includes an updated gnulib?https://www.lrde.epita.fr/~akim/private/bison/bison-3.8.1.27-dd6e.tar.gz https://www.lrde.epita.fr/~akim/private/bison/bison-3.8.1.27-dd6e.tar.lz https://www.lrde.epita.fr/~akim/private/bison/bison-3.8.1.27-dd6e.tar.xz
Thanks for the quick response Akim, will try that out ASAP!The only information I forgot to include was that I copied your patch to revert the autoconf upgrade from 2.68 to 2.71 as Cygwin currently only has up to 2.69.
If it does not work any better, we'll probably have to dive into gnulib.
Spent part of yesterday there!Will later be trying to rebuild fatal-signal.c in the released version with -E to see what the expansions of gl_lock_lock, pthread_in_use, and the value of glthread_in use look like.
Sorry to report still consistent failure mode, symptom, and location. Please see attached.Modified to run from below the non-standard SRC_DIR names, continue, step to get failure, bt, then quit.
Still building with mature gcc 10.2.0 x86_64-pc-cygwin-gcc-10: $ shasum /usr/bin/{x86_64-pc-cygwin-,}gcc{,-10} 94da957d45d705e214bd3229f708c3e90fa92d00 */usr/bin/x86_64-pc-cygwin-gcc 94da957d45d705e214bd3229f708c3e90fa92d00 */usr/bin/x86_64-pc-cygwin-gcc-10 94da957d45d705e214bd3229f708c3e90fa92d00 */usr/bin/gccRebuilt fatal-signal.c with gcc -E -o fatal-signal.i, and added some diagnostic prints to gdb script, and added headers and comments to aid memory.
Attached the relevant extract of fatal-signal.i(block_fata_signals) plus the whole file, scripts, and log.
Please let me know what else would help us get to the bottom of this! -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada This email may be disturbing to some readers as it contains too much technical detail. Reader discretion is advised. [Data in binary units and prefixes, physical quantities in SI.]
bison-segv-cygwin-64-fatal-signal-build.sh
Description: Text document
bison-segv-cygwin-64-fatal-signal.i
Description: Text document
bison-segv-cygwin-64-gdb.sh
Description: Text document
bison-segv-cygwin-64.gdb
Description: Text document
bison-segv-cygwin-64-gdb.log
Description: Text document
fatal-signal.i
Description: Text document
[Prev in Thread] | Current Thread | [Next in Thread] |