Re: bison cygport test segv under Cygwin 64 at fatal-signal.c:318

[Achim Gratz <Stromeko@nexgo.de>]

Brian Inglis writes:
>>> Thread 1 "bison" hit Breakpoint 10, block_fatal_signals () at
>>> /usr/src/debug/bison-3.8.1-1/lib/fatal-signal.c:318
>>> 318       if (mt) gl_lock_lock (fatal_signals_block_lock);
>>> Continuing.
>>>
>>> Thread 1 "bison" received signal SIGSEGV, Segmentation fault.
>>> 0x0000000100000000 in ?? ()
>>> #0  0x0000000100000000 in ?? ()
>>> Backtrace stopped: previous frame identical to this frame (corrupt stack?)
>
>> Well, since you already know where the SEGV hits: what is the diff to the
>> working 3.7.6 version? The sources for this get generated, so you need
>> to check the build directories.
>
> Worse, as neither gnulib/ nor lib/ sources are included in the repo,
> except for their .gitignore files, and only /lib in the tarball, I can 
> only compare the 1.5MB of diffs on 36000 lines, which also span
> internal versions 3.7.90 and 3.7.91, and hope that I can spot
> something relevant!

You only need to look at lib/fatal-signal.c and how that differs
between the working and non-working build as a first step.  If there's
nothing obvious there, you need to look at the call chain that's
involved in the crash, of course.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Samples for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra